[syslog-ng] exitcode=6 - explanation please

Sandor Geller Sandor.Geller at morganstanley.com
Thu Jun 6 10:59:48 CEST 2013

It's in lib/gprocess.c

The supervisor process sends SIGABRT (most likely to dump core for further
analysis) and switches to SIGKILL later when the daemon is still there. I
don't see that the OSE could enter that code path so I assume you're using
PE so I'm sure the BalaBit guys will follow up with you quite soon.

On Wed, Jun 5, 2013 at 10:31 PM, Evan Rempel <erempel at uvic.ca> wrote:

>  From time to time it seems as though syslog-ng crashes, and our logs show
> supervise/syslog-ng[30493]: Daemon exited due to a
> deadlock/signal/failure, restarting; exitcode='6'
> and then the syslog-ng process is restarted.
> Does the exitcode=6 from the syslog-ng process indicate that a SIGABRT was
> received by syslog-ng?
> If not, then what does it mean?
> If it does, I am trying to figure out who would send SIGABRT to the
> process. This is an uncommon signal
> for the OS to send it (unlike SIGSEGV os SIGBUS) and no human sent it a
> signal.
> Can anyone help me understand where the SIGABRT comes from?
> Evan.
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation:
> http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20130606/018022c6/attachment.htm 

More information about the syslog-ng mailing list