[syslog-ng] [Bug 260] exit with code 134

[bugzilla at bugzilla.balabit.com]

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





--- Comment #4 from Evan Rempel <erempel at uvic.ca>  2013-11-19 18:01:27 ---
2013-11-15T09:15:00-08:00 X daemon.info syslog-ng-stats: server stopping on socket "/var/local/syslog-ng.server.ctl"
2013-11-15T09:15:00-08:00 X daemon.info syslog-ng-stats: server starting on socket "/var/local/syslog-ng.server.ctl"
2013-11-15T09:15:01-08:00 X daemon.info syslog-ng-stats: server stopping on socket "/var/local/syslog-ng.server.ctl"
2013-11-15T09:15:01-08:00 X daemon.crit supervise/syslog-ng[16298]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='134'

It only seems to exit during a reload. We have a program destination that logs when it stops and when it starts.
It looks like the reload resulted in the stop/start, and then the crash occurs.

Just thinking about how our 12 sysadmins work and possibly reload syslog-ng. What happens if a HUP is received prior to completing the
reload from a previous HUP?

I have placed two more core files into the same folder as the first. You should be able to download them.

I'll look at getting an strace, but on our production system I think it will be too cpu intensive and/or the output too large.

Any particular strace flags you want or need?


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