[syslog-ng] Interesting issue with syslog-ng 3.3
Gergely Nagy
algernon at madhouse-project.org
Tue Aug 30 23:40:54 CEST 2011
Paul Krizak <paul.krizak at amd.com> writes:
> We had this problem at AMD. The problem turned out to be that
> /dev/console was attached to a device (an iLO in our case) that went
> offline occasionally and would block on writes. We fixed it by updating
> our syslog-ng.conf to write to the console using a pipe() directive
> instead of file().
>
> You may have something similar, especially if there are occasional
> messages that get routed to /dev/console (or any other pipe/device that
> may block).
Hmm, that sounds like a good idea. I do have stuff going to
/dev/console, and I believe messages do get routed there from time to
time. I'll tweak my config and see if it helps.
Thanks!
--
|8]
More information about the syslog-ng
mailing list