[syslog-ng] Random crash in the main thread
som shukla
somj.shukla at gmail.com
Thu Jun 28 06:56:58 UTC 2018
Hi Guys,
Recently we came up with a crash in syslog-ng with following back trace.
rogram terminated with signal SIGBUS, Bus error.
#0 0x00007f03e00b4f7c in ?? () from /usr/lib64/libsyslog-ng.so.0
(gdb) (gdb) (gdb) (gdb) (gdb) #0 0x00007f03e00b4f7c in ?? () from
/usr/lib64/libsyslog-ng.so.0
No symbol table info available.
#1 0x00007f03e00b5a27 in persist_state_start () from
/usr/lib64/libsyslog-ng.so.0
No symbol table info available.
#2 0x00007f03e00a3d7a in cfg_initial_init () from
/usr/lib64/libsyslog-ng.so.0
No symbol table info available.
#3 0x00000000004028e0 in initial_init ()
No symbol table info available.
#4 0x0000000000402a36 in main ()
I thought it to be similar to the this issue
https://github.com/balabit/syslog-ng/issues/716 ,but I'm not sure if this
is really the same.
Has somebody come up with similar issue
Thanks
Somji
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20180628/e10d3c7e/attachment.html>
More information about the syslog-ng
mailing list