syslog-ng dying after kill -HUP
Now experimenting with 1.5.16. Works OK except it consistently dies with a Segmentation Fault after a kill -HUP. This is on a RH 7.2 system. I ran it with the -d option, and the fault occurs after printing io.c: listening on fd 3 io.c: Preparing fd 4 for reading io.c: listening on fd 5 Segmentation fault Any pointers would be greatly appreciated.
Hi! On Fri, Apr 19, 2002 at 03:46:31PM -0400, Robert Berlinger wrote:
Now experimenting with 1.5.16. Works OK except it consistently dies with a Segmentation Fault after a kill -HUP. This is on a RH 7.2 system.
I don't have a solution for your problem, but I am experiencing the same. I'm running syslog-ng on Solaris8, btw. I found out that downgrading to syslog-ng 1.5.15 did NOT solve the problem until I also downgraded to libol 0.3.1. So it is probably a problem with libol. Greetings Gert
On Thu, Apr 25, 2002 at 09:16:01AM +0200, Gert Menke wrote:
Hi!
On Fri, Apr 19, 2002 at 03:46:31PM -0400, Robert Berlinger wrote:
Now experimenting with 1.5.16. Works OK except it consistently dies with a Segmentation Fault after a kill -HUP. This is on a RH 7.2 system.
I don't have a solution for your problem, but I am experiencing the same. I'm running syslog-ng on Solaris8, btw. I found out that downgrading to syslog-ng 1.5.15 did NOT solve the problem until I also downgraded to libol 0.3.1. So it is probably a problem with libol.
Can you provide me with a backtrace? (compile with --with-debug, enable core files, and gdb syslog-ng core, bt command within gdb) -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (3)
-
Balazs Scheidler
-
Gert Menke
-
Robert Berlinger