<p dir="ltr">It might b a failed assertion by the child.</p>
<div class="gmail_quote">On Jun 6, 2013 5:06 PM, "Evan Rempel" <<a href="mailto:erempel@uvic.ca">erempel@uvic.ca</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Two comments.<br>
<br>
1. I am running the OSE, so it would seem that the OSE can enter that code path :-)<br>
<br>
2. Under what conditions would the supervisor send a SIGABRT to its child?<br>
<br>
Evan.<br>
<br>
On 06/06/2013 01:59 AM, Sandor Geller wrote:<br>
> 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>
><br>
><br>
> On Wed, Jun 5, 2013 at 10:31 PM, Evan Rempel <<a href="mailto:erempel@uvic.ca">erempel@uvic.ca</a> <mailto:<a href="mailto:erempel@uvic.ca">erempel@uvic.ca</a>>> wrote:<br>
><br>
> 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>
><br>
><br>
><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>
<br>
<br>
--<br>
Evan Rempel <a href="mailto:erempel@uvic.ca">erempel@uvic.ca</a><br>
Senior Systems Administrator <a href="tel:250.721.7691" value="+12507217691">250.721.7691</a><br>
Data Centre Services, University Systems, University of Victoria<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>