W dniu 2011-07-02 13:05, Rainer Gerhards pisze:
> Did you run rsyslogd as root? As far as I can see, no listeners could be
> activated. Obviously, error reporting needs to be improved, will check that
> out.

Yes, i run rsyslogd as root. It was started by the same init script as
earlier version. I don't know is it important, i'm using hardened kernel
(grsecurity patch).

>> rsyslogd-2040: fatal error on disk queue 'action 1 queue[DA]',
>> emergency
>> switch to direct mode [try http://www.rsyslog.com/e/2
>> 040 ]
> 
> As I guessed, the queue files are not OK. The .qi file requests buffer file
> 1251, which seems not to be present (or not accessible to the account you run
> rsyslog under). This can lead to the rest of the problem you see.

I've often such problem. When OS crashed or i have to stop rsyslogd
using SIGKILL instead SIGTERM. But with version 5.6.5 it has only one
side effect, rsyglogd didn't send queue to another rsyslogd. V5.6.5
quits cleanly after SIGTERM.

[from later email]
> Sorry, I should have checked that first. The debug log indicates that
> the
> error message
> "imudp: no listeners could be started, input not activated"
> was generated right in front of the message you quote. Wasn't that
> present
> inside your log?

Indeed, it was present. (don't trust users, they always skip something
from log...).

This should be all messages generated by git-version:

2011-06-30T15:26:12.613744+02:00 hermes rsyslogd: [origin
software="rsyslogd" swVersion="6.3.1" x-pid="29536"
x-info="http://www.rsyslog.com";] start
2011-06-30T15:26:12.578971+02:00 hermes rsyslogd: imklog 6.3.1, log
source = /proc/kmsg started.
2011-06-30T15:26:12.579117+02:00 hermes rsyslogd: imudp: no listeners
could be started, input not activated.
: No such file or directory
2011-06-30T15:26:12.579124+02:00 hermes rsyslogd3: activation of module
imudp.so failed [try http://www.rsyslog.com/e/-3 ]
2011-06-30T15:26:12.579385+02:00 hermes rsyslogd3: activation of module
imtcp.so failed [try http://www.rsyslog.com/e/-3 ]
2011-06-30T15:26:12.615118+02:00 hermes rsyslogd-2040: fatal error on
disk queue 'action 1 queue[DA]', emergency switch to direct mode [try
http://www.rsyslog
.com/e/2040 ]

Thanks for help.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to