[syslog-ng] [Bug 161] Syslog-ng stops processing after reload

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=161





--- Comment #5 from Patrick <bugzilla.syslogng at feystorm.net>  2012-04-27 19:38:30 ---
Ok, so I think you are correct on this, it wasnt hanging, it was just taking forever to write out to NFS. I didnt expect syslog-ng to have that much unwritten
data as I have the flush_timeout and flush_line settings set pretty low on all destinations. However syslog-ng maintains about 2000 open files at any given
time, so 2000 files with just a little bit of data could add up.

I think this might also be loosely related to bug 175 which I just opened. It might be trying to write a ton of data causing the linux dirty writes thresholds
to be exceeded and triggering a pdflush, which then in turn causes syslog-ng to hang until the flush is complete.

Its probably safe to consider this bug invalid. I'll see what the behavior is after bug 175 is fixed.


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.