[syslog-ng] [Bug 253] Segfault when reloading configuration

[Balazs Scheidler]

This seems like a failing assertion as 138 indicates a SIGABRT

Do you happen to have a core file for that? If you do can you pls open a
new ticket, seems unrelated to this.
Thanks.
On Nov 6, 2013 6:34 AM, <bugzilla at bugzilla.balabit.com> wrote:

> https://bugzilla.balabit.com/show_bug.cgi?id=253
>
>
> Evan Rempel <erempel at uvic.ca> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |erempel at uvic.ca
>
>
>
>
> --- Comment #13 from Evan Rempel <erempel at uvic.ca>  2013-11-06 06:34:31
> ---
> Not exactly a segmentation fault, but I can't explain it.
>
> I just did a reload on version 3.4.4 (with latest patches) and triggered
>
> 2013-11-05T21:24:33-08:00 host daemon.crit supervise/syslog-ng[25895]:
> Daemon exited due to a deadlock/signal/failure, restarting; exitcode='134'
>
> Is it possible that the return code of syslog-ng is somehow linked to the
> return code of a child program destination?
>
>
> --
> Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are watching all bug changes.
>
> ______________________________________________________________________________
> 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/20131106/ddfbe027/attachment-0001.htm