[syslog-ng]syslog-ng dying randomly?

John Morrissey [email protected]
Wed, 15 May 2002 13:15:41 -0400


On Wed, May 15, 2002 at 10:20:45AM +0200, Balazs Scheidler wrote:
% sorry to repeat myself, but this patch adds even more sanity checking:

I patched libol on a local machine and started syslog-ng. It ran for much
longer than normal, but then I realized that it could reach the syslog hub.
When I removed its access to the syslog hub, syslog-ng died (segfaulted)
within a couple minutes with the following internal messages logged:

May 15 12:44:09 serviceman01 syslog-ng[9566]: syslog-ng version 1.4.14 starting
May 15 12:44:09 serviceman01 syslog-ng: syslog-ng startup succeeded
May 15 12:44:50 serviceman01 syslog-ng[9566]: Connection broken, reopening in 60 seconds
May 15 12:49:22 serviceman01 syslog-ng[9566]: Connection broken, reopening in 60 seconds

Backtrace was the same. There were no assertions logged; would they be
syslogged? It looks like syslog-ng gets wedged somehow before it dies and
might not be able to log anything.

thanks for your help,
john
-- 
John Morrissey          _o            /\         ----  __o
[email protected]        _-< \_          /  \       ----  <  \,
www.horde.net/    __(_)/_(_)________/    \_______(_) /_(_)__