[syslog-ng] [Bug 34] After sighup master doe not write to logs, but clients think the server is writing to the logs

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Sat Feb 28 14:55:33 CET 2009


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





--- Comment #1 from Balazs Scheidler <bazsi at balabit.hu>  2009-02-28 14:55:33 ---
Hmm.. can you please give me more details about your syslog-ng installation?

E.g. I'd definitely need the version number, how you compiled your syslog-ng (e.g. is it your own compilation, or you got the binary from somewhere). 

Also I'd first check that syslog-ng is indeed receiving the SIGHUP signal. Most related issues are caused by the fact that syslog-ng does not receive 
the SIGHUP signal and is still writing to the old (probably deleted logfile).


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


More information about the syslog-ng mailing list