[syslog-ng] 3.0.3: Accessing unix-dgram source appears to break all logging

Markus Stalder ms2 at lightupnet.de
Thu Aug 6 10:44:15 CEST 2009

> On Wed, 2009-08-05 at 16:56 +0200, Sandor Geller wrote:
>> You're referencing exactly the same sources (like /dev/log,
>> /proc/kmsg)? This config is horribly broken. I can't imagine how was
>> syslog-ng 2.0.9 working with such a config. You should eliminate all
>> duplicated sources. You can add as many log {} sections using the same
>> source definition as you wish.
> the configuration is indeed broken, you basically tell syslog-ng to
> open /dev/log _twice_, what's worse: in a different mode (stream vs.
> dgram).  Also the linux kernel does not like when there are
> multiple /proc/kmsg readers, syslog-ng might deadlock in this scenario.
> I'm not sure syslog-ng hangs or simply the applications trying to send
> messages cease to do so, you could find that out using strace (either
> the application or syslog-ng, or both)

Thanks guys, that was the feedback I was hoping for! I'll remove the
unix-dgram source then...


More information about the syslog-ng mailing list