Rudder

could it be a file permission issue ? http://serverfault.com/questions/596558/ubuntu-14-04-system-logging
if the file as not the right permission, then rsyslog fails to write in the file and skip ?

I had to manually restart rsyslog for it to work, but not to reboot (on Rudder 3.0.7 and ubuntu 14.04)
however, services were super slow at start

ok, restarting rsyslog unclog some messages, but not for a long time ...

restarting rsyslog does
Jul 13 17:20:26 server rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8060" x-info="http://www.rsyslog.com"] exiting on signal 15.
Jul 13 17:20:26 server rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8347" x-info="http://www.rsyslog.com"] start
Jul 13 17:20:26 server rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 13 17:20:26 server rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 13 17:20:26 server rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 13 17:20:26 server rsyslogd: rsyslogd's groupid changed to 104
Jul 13 17:20:26 server rsyslogd: rsyslogd's userid changed to 101
Jul 13 17:20:27 server rudder⁸¹³¹: R: @server-roles@result_success@server-roles@server-roles-directive@1@Check logrotate configuration@None@2015-07-13 17:20:25+00:00##root@#The logrotate configuration is correct

send it seems to stop

one important step is to
chown syslog:adm /var/log/rudder/reports and /var/log/rudder/ldap

it seems that the rsyslog stops or block itself at reception of rudder logs when inserting them in database.
if I comment out the writing to DB, it does work find, otherwise it blocks itself

restarting the ubuntu server did fix the issue
log don't tell me why it changed
I git init /etc before, and I only get very minor changes (caches for apparmor, or host file changing, and nologin file deleted)

The problem is in ompgsql, and was fixed in rsyslog 7.6.0 and 7.4.10: http://www.rsyslog.com/changelog-for-7-6-0-v7-stable/

ompgsql bugfix: improper handling of auto-backgrounding mode
If rsyslog was set to auto-background itself (default code behaviour, but many distros now turn it off for good reason), ompgsql could not properly connect. This could even lead to a segfault. The core reason was that a PG session handle was kept open over a fork, something that is explicitely forbidden in the PG API.

The fix is available here, and was tested on 7.4.4/ubuntu 14.04.

Applied in changeset rudder-packages|a579a354b8cf74f2b7a7dd5ee6f595f1311999a1.

Applied in changeset rudder-packages|9c332cacec3566923adb4cb77b9b31a45f20a9e3.