Your message dated Fri, 13 Apr 2012 16:28:01 -0400
with message-id <[email protected]>
and subject line Re: snmpd: init script using wrong return code on option
"status"
has caused the Debian Bug report #615846,
regarding snmpd: init script using wrong return code on option "status"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
615846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615846
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: snmpd
Version: 5.4.3~dfsg-2
Severity: normal
| If the status action is requested, the init script will return the following
exit status codes.
|
| 0 program is running or service is OK
| 1 program is dead and /var/run pid file exists
| 2 program is dead and /var/lock lock file exists
| 3 program is not running
| 4 program or service status is unknown
--
http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
snmpd's init script uses status_of_proc in the status option code
but due to lack of pid files (see #611668) this seems to go wrong:
# /etc/init.d/snmpd status
snmpd is not running ... failed!
snmptrapd is not running ... failed!
# echo $?
1
This means snmpd can't be integrated in cluster setups with its
current initscript, see
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ap-lsb.html
regards,
-mika-
--- End Message ---
--- Begin Message ---
Version: 5.4.3~dfsg-2
On Thu, 2012-04-12 at 23:32 +0200, Michael Prokop wrote:
> * Ignace Mouzannar [Thu Apr 12, 2012 at 12:11:57PM -0400]:
> > Are you still experiencing the same issue?
>
> No, I sadly (well, luckily on the other hand) can no longer
> reproduce this issue on current squeeze installations.
>
> Feel free to close the bugreport.
Thanks for your prompt answer.
As I am unable to to reproduce it on multiple Squeeze installations;
they all exit with code 3; as you suggested, I'm closing this bug
report.
Cheers,
Ignace M
--- End Message ---
