Bug 480828

Summary: Zero-length pid files cause resource start failures
Product: [Retired] Red Hat Cluster Suite Reporter: Marek Grac <mgrac>
Component: rgmanagerAssignee: Marek Grac <mgrac>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 4CC: cluster-maint, cmarthal, edamato, nicolas.monnet
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 474444 Environment:
Last Closed: 2009-05-18 21:13:37 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: 474444    
Bug Blocks:    

Description Marek Grac 2009-01-20 19:11:20 UTC 
+++ This bug was initially created as a clone of Bug #474444 +++

Created an attachment (id=325599)
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 3 errata-xmlrpc 2009-05-18 21:13:37 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/RHBA-2009-1048.html