<div dir="ltr">It's in lib/gprocess.c<br><br>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.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 5, 2013 at 10:31 PM, Evan Rempel <span dir="ltr"><<a href="mailto:erempel@uvic.ca" target="_blank">erempel@uvic.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
From time to time it seems as though syslog-ng crashes, and our logs show<br>
<br>
supervise/syslog-ng[30493]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='6'<br>
<br>
and then the syslog-ng process is restarted.<br>
<br>
<br>
Does the exitcode=6 from the syslog-ng process indicate that a SIGABRT was received by syslog-ng?<br>
<br>
If not, then what does it mean?<br>
<br>
If it does, I am trying to figure out who would send SIGABRT to the process. This is an uncommon signal<br>
for the OS to send it (unlike SIGSEGV os SIGBUS) and no human sent it a signal.<br>
<br>
Can anyone help me understand where the SIGABRT comes from?<br>
<br>
Evan.<br>
______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
<br>
</blockquote></div><br></div>