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

Lennert Buytenhek buytenh at wantstofly.org
Tue Aug 28 17:55:00 CEST 2012


On Tue, Aug 28, 2012 at 05:38:51PM +0200, bugzilla at bugzilla.balabit.com wrote:

> 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'

Right, but does the syslog-ng daemon output anything to its
controlling terminal?  (Can you run it by hand from a terminal?)


More information about the syslog-ng mailing list