[syslog-ng] [Bug 24] New: .pid file not set correctly (STOP not working)

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Fri Dec 5 12:53:43 CET 2008


           Summary: .pid file not set correctly (STOP not working)
           Product: syslog-ng
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: unspecified
         Component: syslog-ng
        AssignedTo: bazsi at balabit.hu
        ReportedBy: man at inspektsecurity.com
Type of the Report: ---
   Estimated Hours: 0.0


in installed syslog-ng 3.0.1 PE (syslog-ng-premium-edition-3.0.1-linux-i386.run).
The installation is on a CentOS 5 system (RedHat spin-off).

Although the program itself works fine, the RC scripts STOP command does not work.

I traced the problem down to the .pid file not being set correctly.
According to the RC script the .pid file shoud be in:

resulting in the below when running STOP/RESTART
[root at test-server:~] /etc/init.d/syslog-ng restart
-n Restarting syslog-ng: 
-n Stopping syslog-ng: 
-n Starting syslog-ng: 
Error binding socket; addr='AF_INET(', error='Address already in use (98)'
Error initializing source driver; source='tcp_input_syslog', id='tcp_input_syslog#0'
Error initializing message pipeline;
I found out that the pid file set is actually:

So changing the RC script to:

seems to work.


Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the syslog-ng mailing list