It might b a failed assertion by the child.
Two comments.
1. I am running the OSE, so it would seem that the OSE can enter that code path :-)
2. Under what conditions would the supervisor send a SIGABRT to its child?
Evan.
On 06/06/2013 01:59 AM, Sandor Geller wrote:
> 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@uvic.ca <mailto:erempel@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
>
>
>
>
> ______________________________________________________________________________
> 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
>
--
Evan Rempel erempel@uvic.ca
Senior Systems Administrator 250.721.7691
Data Centre Services, University Systems, University of Victoria
______________________________________________________________________________
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