Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 474444

Summary: Zero-length pid files cause resource start failures
Product: Red Hat Enterprise Linux 5 Reporter: Lon Hohberger <lhh>
Component: rgmanagerAssignee: Marek Grac <mgrac>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3CC: cluster-maint, edamato, nicolas.monnet
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 480828 (view as bug list) Environment:
Last Closed: 2009-09-02 11:05:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 480828    
Attachments:
Description Flags
Preliminary patch
none
Final patch none

Description Lon Hohberger 2008-12-03 21:12:49 UTC 
Created attachment 325599 [details]
Preliminary patch

config-utils.sh has check_pid_file() which is a little too zealous in its checks.

For example, if a PID file exists but is of zero length, a start for a service might fail.

This patch unlinks a zero-length PID file, since it's not useful data.  I don't know whether or not it's correct to do this generally.

This issue was first reported in bug 462910 .
Comment 1 Marek Grac 2009-01-20 19:27:04 UTC 
Created attachment 329501 [details]
Final patch

Patch follows the idea of preliminary patch. Test & remove were moved to better section as there is a bug in proposed patch (-z will test for length of string; not length of filename).
Comment 4 errata-xmlrpc 2009-09-02 11:05:22 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2009-1339.html