This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1B0EC.FCA1B0F0 Content-Type: text/plain; charset="iso-8859-1" Are you referring to the SIGHUP bugs(s)? -----Original Message----- From: Ed Ravin [mailto:eravin@panix.com] Sent: Friday, February 08, 2002 12:40 PM To: syslog-ng@lists.balabit.hu Subject: Re: [syslog-ng]syslog-ng mysteriously exits John Coke writes: > 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. So my next question is - where's the core dump? It should show up in the current directory of the daemon. Use "lsof" while the daemon is running to see what directory it is in, and check there. Or do a global find and hunt it down. Also, have you tried upgrading to the latest syslog-ng (1.5.14 or so)? Except for one small bug :-) it's worked pretty well for me. _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng ------_=_NextPart_001_01C1B0EC.FCA1B0F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">RE: [syslog-ng]syslog-ng mysteriously exits Are you referring to the SIGHUP bugs(s)?
-----Original Message-----
From: Ed Ravin [mailto:eravin@panix.com]
Sent: Friday, February 08, 2002 12:40 PM
To: syslog-ng@lists.balabit.hu
Subject: Re: [syslog-ng]syslog-ng mysteriously = exits
John Coke writes:
> = getpid() &nbs= p; &nbs= p; =3D 3616
> = time(NULL) &n= bsp; &n= bsp; =3D 1013148201
> rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = =3D 0
> = getpid() &nbs= p; &nbs= p; =3D 3616
> kill(3616, = SIGABRT) &nbs= p; =3D 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.So my next question is - where's the core dump? = It should show up in
the current directory of the daemon. Use = "lsof" while the daemon is
running to see what directory it is in, and check = there. Or do a
global find and hunt it down.Also, have you tried upgrading to the latest = syslog-ng (1.5.14 or so)?
Except for one small bug :-) it's worked pretty well = for me.
_______________________________________________
------_=_NextPart_001_01C1B0EC.FCA1B0F0--
syslog-ng maillist - = syslog-ng@lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng