[Bug 199] New: syslog-ng 3.3.6. 90 sometimes exits on SIGHUP on Solaris 10 SPARC
https://bugzilla.balabit.com/show_bug.cgi?id=199 Summary: syslog-ng 3.3.6.90 sometimes exits on SIGHUP on Solaris 10 SPARC Product: syslog-ng Version: 3.3.x Platform: Other OS/Version: Solaris Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: irwin@princeton.edu Type of the Report: bug Estimated Hours: 0.0 Created an attachment (id=66) --> (https://bugzilla.balabit.com/attachment.cgi?id=66) configure.out Version: syslog-ng 3.3.6.90 Platform: Solaris 10 on SPARC I've been running syslog-ng 3.0.6 fine for several years. I've been trying to upgrade to 3.3.latest. When I upgraded to 3.3.6, syslog-ng would sometimes quit and dump core unexpectedly when I sent it SIGHUP as part of log file rotation. I figured it might be an ivykis issue perhaps related to https://bugzilla.balabit.com/show_bug.cgi?id=190 , so I've just tried upgrading to 3.3.6.90. But the error I see remains the same. Log message: Sep 26 03:00:03 example.org supervise/syslog-ng[23280]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='131' Here's the core dump's backtrace: gdb /usr/local/sbin/syslog-ng /var/core/core.syslog-ng.0.23281 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 3, Quit. #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=0xffbffd4c) at main.c:263 -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=199 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |algernon@balabit.hu AssignedTo|bazsi@balabit.hu |algernon@balabit.hu --- Comment #1 from Gergely Nagy <algernon@balabit.hu> 2012-09-26 17:50:31 --- This is interesting. The exit happens due to syslog-ng signalling itself with SIGQUIT, because it ends up in a branch where the new configuration could not be loaded, and reverting to the old one failed aswell. I'll try to reproduce it myself, but in the meantime, could you perhaps change line 518 of lib/mainloop.c to send a SIGABRT instead of a SIGQUIT? If you enable core dumps afterwards, then syslog-ng should dump a nice core, which might help us figure out what went wrong. Also, are there any error messages coming from syslog-ng in the logs by any chance? -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=199 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=199 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bazsi@balabit.hu --- Comment #2 from Balazs Scheidler <bazsi@balabit.hu> 2012-09-27 12:42:01 --- This happens because syslog-ng doesn't properly close /dev/log at SIGHUP. the OS permits 16 concurrent opens to this device, if that is reached, this is what happens. Just an idea, there's a separate ticket on this, but I had no time to fix that. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=199 --- Comment #3 from Irwin Tillman <irwin@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.
https://bugzilla.balabit.com/show_bug.cgi?id=199 --- Comment #4 from Irwin Tillman <irwin@princeton.edu> 2012-09-27 19:08:25 --- Yes, in reviewing my logs, I see that the failures are happening on every 16th SIGHUP after a (re)start. So this is a dupe of https://bugzilla.balabit.com/show_bug.cgi?id=151 -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=199 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution| |DUPLICATE Status|ASSIGNED |RESOLVED --- Comment #5 from Gergely Nagy <algernon@balabit.hu> 2012-09-28 09:28:18 --- *** This bug has been marked as a duplicate of bug 151 *** -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
bugzilla＠bugzilla.balabit.com