Hi All, I have configured a syslog-ng client(Syslog-ng 2.0rc1) on Linux. Afer couple of hours it stops working. It happens quiet often. If I check the daemen status( /etc/init.d/syslog-ng status), its says, Syslog-ng dead, but PID exists. Can anyone help me to resolve this issue. Thanks in advance. -Rajeesh
On Mon, 2007-01-22 at 12:09 +0530, Padmanabhan, Rajeesh (GE Healthcare) wrote:
Hi All,
I have configured a syslog-ng client(Syslog-ng 2.0rc1) on Linux. Afer couple of hours it stops working. It happens quiet often. If I check the daemen status( /etc/init.d/syslog-ng status), its says,
Syslog-ng dead, but PID exists.
Can anyone help me to resolve this issue. Thanks in advance.
first, please try using the latest stable release, which is 2.0.1 (not 2.0rc1). You can check the list of user-visible changes in the file named NEWS in the root of the distribution tarball. Second if it still crashes, compile syslog-ng with debugging symbols (--enable-debug configure option), enable core dumping (ulimit -c unlimited) before starting syslog-ng, and look for the core file once the daemon has crashed. (the core file is saved to the current directory of the daemon, it has to be writable by the user running syslog-ng) Once you have a core file: gdb /path/to/syslog-ng -c /path/to/core-file (gdb) bt And send its output to this list. -- Bazsi
participants (2)
-
Balazs Scheidler
-
Padmanabhan, Rajeesh (GE Healthcare)