Bug 514039

Summary: apache.sh will not stop cleanly if "pkill httpd" is ran
Product: Red Hat Enterprise Linux 5 Reporter: Shane Bradley <sbradley>
Component: rgmanagerAssignee: Marek Grac <mgrac>
Status: CLOSED DUPLICATE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 5.5CC: cluster-maint, djansa, edamato, tao
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-21 21:06:09 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: 512055    
Attachments:
Description Flags
Patch that checks for existence of .pid file none

Description Shane Bradley 2009-07-27 18:25:11 UTC 
Description of problem:

If a clustered service is running with "apache" as a resource and then
"pkill httpd" is ran the service will got into a failed state.

The reason that service goes into the failed state is because the pid
file was already cleaned up and no longer exist. Thus checking for
existence of the pid file will always fail.

The solution is to only call the "stop_generic $PIDFILE" if the pid
file actual exist.

The service will then go into failed state.

Version-Release number of selected component (if applicable):
rgmanager-2.0.46-1.el5_3.3

How reproducible:
Every time.

Steps to Reproduce:
1. create apache resource in a service
2. start service
3. pkill httpd
4. clustat
  
Actual results:
The service will be in failed state and does not recover correctly.

Expected results:
The service should be restarted correctly.

Additional info:
Patch to resolve the issue is attached to the bz.
Comment 1 Shane Bradley 2009-07-27 18:25:48 UTC 
Created attachment 355302 [details]
Patch that checks for existence of .pid file
Comment 2 Lon Hohberger 2009-08-21 17:47:44 UTC 
This really looks like a duplicate of 

https://bugzilla.redhat.com/show_bug.cgi?id=449394
Comment 3 Lon Hohberger 2009-08-21 21:06:09 UTC 

*** This bug has been marked as a duplicate of bug 449394 ***