[syslog-ng] problem with syslog-ng hanging on saturday after working all week

Balazs Scheidler bazsi at balabit.hu
Fri Oct 6 09:58:55 CEST 2006

On Mon, 2006-09-18 at 14:42 -0400, Valdis.Kletnieks at vt.edu wrote:
> On Mon, 18 Sep 2006 12:36:51 CDT, Steven Meacham said:
> > Need help. My syslog-ng is hanging on Saturdays. It is like the service just
> > stops responding even though it is running
> I've seen similar oddness with other networking that had to go through a
> stateful firewall - worked fine as long as there was activity, but during
> long inactive sessions the firewall would time out the state entries and
> treat subsequent packets as "not part of a known connection".  Does it
> keep working on Saturdays if you create a dummy program that just generates
> a throw-away log message once a minute?  If so, then your system has an
> inactive timer that's going off and shooting things down.
> Oh yeah, and check for cronjobs running just before the last message when
> it stops running.  If it rolls over and dies at 5:03AM every Saturday, it's
> time to check those 5AM cronjobs. ;)

Also, you should check whether there are two programs reading /proc/kmsg
in parallel, this is a known problem, the kernel does not support
non-blocking I/O for /proc/kmsg and even though syslog-ng enables
non-blocking I/O for its fds it still blocks.


More information about the syslog-ng mailing list