status_of_proc is returning incorrect error code causing pacemaker to fail monitor cycle
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lsb (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: lsb
Trying to manage bacula-director via pacemaker fails due to a bug present in /lib/lsb/
pacemaker relies on init scripts to be compliant with the lsb standards.
Retrieved from: http://
As per LSB Init compliancy:
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
5-99 reserved for future LSB use
100-149 reserved for distribution use
150-199 reserved for application use
200-254 reserved
Pacemaker runs an /etc/init.
This is a duplicate of bug
https:/
I have applied the patch posted above and I can report it fixes the issue.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: lsb-base 4.0-0ubuntu8 [modified: lib/lsb/
ProcVersionSign
Uname: Linux 2.6.35-23-server x86_64
Architecture: amd64
Date: Wed Jan 12 15:00:04 2011
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
PackageArchitec
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: lsb