Hi, Several of you noted that syslog-ng crashes on SIGHUP sometimes. I'd really like to fix this bug, but I'd need a backtrace of a syslog-ng & libol built with debug information. To create this configure both libol and syslog-ng with the --with-debug configure time option. Have syslog-ng core itself (with ulimit -c unlimited), and send me the results of the following command: gdb syslog-ng -c core bt I may need binaries, the core file and strace results as well, but as a first step the backtrace should be enough. Could anybody help? thanks. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
Balazs Scheidler on Thu 18/01 18:14 +0100:
Several of you noted that syslog-ng crashes on SIGHUP sometimes.
My syslog-ng processes are HUPped daily and have never crashed in at least two months, perhaps three. They aren't HUPped during heavy log periods, but still...you would think it would have happened by now. Is there some type of usage pattern which triggers this bug?
participants (2)
-
Balazs Scheidler
-
Scott McDermott