[syslog-ng] [Bug 190] syslog-ng with TCP source, fails to shutdown properly, and generates core dump

[bugzilla at bugzilla.balabit.com]

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


Marvin Nipper <marvin.nipper at stream.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|3.3.7                       |---




--- Comment #3 from Marvin Nipper <marvin.nipper at stream.com>  2012-08-28 17:38:52 ---
Regarding Lennert's query about standard output when this happens.  My reply:


Duh!!!  Thanks for the kick in the tail, I should have looked there, and recorded that.  Brain now engaged....

This is what popped up in the /var/adm/messages file:
Aug 28 09:51:57 secdevrsn02 genunix: [ID 603404 kern.notice] NOTICE: core_log: syslog-ng[604] core dumped:
/var/core/core_secdevrsn02_syslog-ng_0_0_1346165515_604
Aug 28 09:51:57 secdevrsn02 supervise/syslog-ng[603]: [ID 702911 daemon.crit] Daemon exited due to a deadlock/signal/failure, restarting; exitcode='134'


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