Bug 236204

Summary: rgmanager restarts system when trying to stop it just after it's start
Product: Red Hat Enterprise Linux 5 Reporter: Andrey Mirkin <amirkin>
Component: rgmanagerAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: cluster-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2007-0580 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-07 16:46:01 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:
Attachments:
Description Flags
This patch fixes the problem none

Description Andrey Mirkin 2007-04-12 14:29:13 UTC 
Description of problem:
When trying to stop rgmanager just after it was started rgmanager write to log:
clurgmgrd[8751]: <crit> Watchdog: Daemon died, rebooting...

And after that rgmanger reboot the node.


Version-Release number of selected component (if applicable):
rgmanager-2.0.23-1


How reproducible:
Do "/etc/init.d/rgmanager restart" in cycle

Actual results:
Node is rebooted.

Expected results:
Restarted rgmanager

Additional info:
The problem is that signal handlers are set not right after watchdog is started.
So when we are sending TERM signal to main process, it will exit and watchdog
will get exit status.
Comment 1 Andrey Mirkin 2007-04-12 14:29:14 UTC 
Created attachment 152452 [details]
This patch fixes the problem
Comment 2 Lon Hohberger 2007-04-12 17:26:20 UTC 
Patch applied to RHEL5 and CVS head.
Comment 4 Kiersten (Kerri) Anderson 2007-04-23 17:25:36 UTC 
Fixing Product Name.  Cluster Suite was integrated into the Enterprise Linux for
version 5.0.
Comment 7 errata-xmlrpc 2007-11-07 16:46:01 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 the 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-2007-0580.html