Cluster nodes rebooting themselves after failing to stop a script resource in RHEL 6
Issue
- A status check fails in our service and during the subsequent stop operation, the script resource fails to stop. The node reboots after this
Mar 8 11:50:33 node2 rgmanager[1763]: status on script "myScript" returned 1 (generic error)
Mar 8 11:50:33 node2 rgmanager[1763]: Stopping service service:myService
Mar 8 11:50:33 node2 rgmanager[3890]: [script] Executing /usr/local/bin/myScript.sh stop
Mar 8 11:50:37 node2 rgmanager[4043]: [script] script:myScript: stop of /usr/local/bin/myScript.sh failed (returned 1)
Mar 8 11:50:37 node2 rgmanager[1763]: stop on script "myScript" returned 1 (generic error)
Mar 8 11:50:37 node2 rgmanager[4160]: [fs] unmounting /myFS
Mar 8 11:50:43 node2 rgmanager[4281]: [fs] unmounting /myFS
Mar 8 11:50:48 node2 rgmanager[4401]: [fs] unmounting /myFS
Mar 8 11:50:49 node2 rgmanager[4446]: [fs] 'umount /myFS' failed, error=1
Mar 8 11:50:49 node2 rgmanager[4468]: [fs] umount failed - REBOOTING
- After adding a script resource the nodes are fencing themsevles
Environment
- Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
- One or more services in
/etc/cluster/cluster.conf
containing an<fs>
resource usingself_fence="on"
(or"1"
).
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.