[bug-notifications] [syslog_ng 0004308]: syslog_ng fails with exit status 2 on shutdown/reboot

Mantis Bug Tracker noreply at opencsw.org
Mon Mar 1 18:13:55 CET 2010


A NOTE has been added to this issue. 
====================================================================== 
http://www.opencsw.org/bugtrack/view.php?id=4308 
====================================================================== 
Reported By:                diget
Assigned To:                maciej
====================================================================== 
Project:                    syslog_ng
Issue ID:                   4308
Category:                   regular use
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             2010-02-26 00:13 CET
Last Modified:              2010-03-01 18:13 CET
====================================================================== 
Summary:                    syslog_ng fails with exit status 2 on
shutdown/reboot
Description: 
On rebooting a Solaris 10u8 (10/09) SPARC machine it complains about
shutting down syslog-ng with the following message:

<timestamp> svc.startd[7]: svc:/network/cswsyslog_ng:default: Method
"/var/opt/csw/svc/method/svc-cswsyslog_ng stop" failed with exit status 2.


With syslog_ng running and running the manifest file by hand, it appears
that the pid file as gone  via the kill -15 and therefore the rm
${PID_FILE} in the stop section complains.  I think adding a "-f" to the rm
would fix the problem.
====================================================================== 

---------------------------------------------------------------------- 
 (0007557) diget (reporter) - 2010-03-01 18:13
 http://www.opencsw.org/bugtrack/view.php?id=4308#c7557 
---------------------------------------------------------------------- 
Upgraded to the 3.0.5 in the experimental area of maciej's.

No more error on disabling the service or rebooting. :)  Fixed.



More information about the bug-notifications mailing list