[syslog-ng]syslog-ng mysteriously exits

[Ed Ravin]

John Coke writes:
> Are you referring to the SIGHUP bugs(s)?

No. I'm referring to assert(3) or the moral equivalent.  See
the relevant man pages.

Any luck in finding the core file?  Also, check your ulimit
settings, you might have core files disabled.

> > getpid()                                = 3616
> > time(NULL)                              = 1013148201
> > rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
> > getpid()                                = 3616
> > kill(3616, SIGABRT)                     = 0
> > --- SIGABRT (Aborted) ---
> > 
> > I have not been able to find a clear picture of what causes SIGABRT.
> 
> This is self-inflicted - note that the process looks up its own process
> ID number (getpid()), diddles the signal mask (I'm guessing it's to
> enable SIGABRT), then kills itself.  syslog-ng has probably detected
> something very wrong, and is trying to leave you a core dump so you
> can figure out what happened.