[syslog-ng] [Bug 199] syslog-ng 3.3.6.90 sometimes exits on SIGHUP on Solaris 10 SPARC

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=199





--- Comment #3 from Irwin Tillman <irwin at princeton.edu>  2012-09-27 17:13:02 ---
I've rebuilt with SIGABRT, and am running with --enable-core
and ulimit core set for 1 GB.

Here's a backtrace from a new failure; it appears similar
to the previous one:

gdb /usr/local/sbin/syslog-ng /var/core/core.syslog-ng.0.10801
GNU gdb (GDB) 7.4
...
Reading symbols from /var/local/sbin/syslog-ng...done.
[New LWP 1]
[New LWP 2]
[New LWP 3]
[Thread debugging using libthread_db enabled]
[New Thread 1 (LWP 1)]
[New Thread 2 (LWP 2)]
[New Thread 3 (LWP 3)]
Core was generated by `/usr/local/sbin/syslog-ng --cfgfile /etc/syslog-ng/main.conf --pidfile /var/run'.
Program terminated with signal 6, Aborted.
#0  0xfef4e068 in kill () from /lib/libc.so.1
(gdb) bt
#0  0xfef4e068 in kill () from /lib/libc.so.1
#1  0xff2b4c24 in main_loop_reload_config_apply () at mainloop.c:518
#2  0xff2b4640 in main_loop_io_worker_sync_call (func=0xff2b4a20 <main_loop_reload_config_apply>) at mainloop.c:455
#3  0xff2d68c8 in iv_signal_event (_this=0xff30ddfc) at iv_signal.c:169
#4  0xff2d62b8 in iv_event_raw_got_event (_this=0xff30de20) at iv_event_raw.c:87
#5  0xff2d3d38 in iv_run_active_list (active=<optimized out>, st=<optimized out>) at iv_main.c:235
#6  iv_main () at iv_main.c:279
#7  0xff2b4474 in main_loop_run () at mainloop.c:735
#8  0x00011538 in main (argc=1, argv=0xffbffd3c) at main.c:263


The only error message written by syslog-ng to the logs was:
  Sep 27 11:00:03 example.org supervise/syslog-ng[10800]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='134'


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.