Bug 163185 - Unknown condition causes fenced to hang on bootup
Unknown condition causes fenced to hang on bootup
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: fence (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jim Parsons
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2005-07-13 16:08 EDT by Henry Harris
Modified: 2009-04-16 16:10 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-22 15:37:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Henry Harris 2005-07-13 16:08:33 EDT
Description of problem: Fenced sometimes hangs indefinitely on bootup

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

How reproducible:  Have not determined exactly how to reproduce.  We have seen 
this a number of times on different clusters.  Most often we see it happen 
after some change to the backend storage -- ie. changing FC HBA's, adding 
LUN's, etc.  When this condition occurs, the only way to recover is to bring 
the node up in single user mode, then disable the cluster daemons, and go to 
run level 5.  At this point you can then start the cluster daemons as usual 
and it seems to work fine.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 2 Christine Caulfield 2005-07-15 05:58:30 EDT
Is it possible to get more information about this at all? 
I suspect the configuration changes are a red herring but they might be
co-incidental with something else, eg the whole cluster being rebooted after
such changes?.

When it next happens can you check for fencing messages in /var/log/messages?
Also, if there are other nodes in the cluster when it happens can you post the
output of "cman_tool services" from them please ?

I'll continue to try to reproduce it here.
Comment 4 Kiersten (Kerri) Anderson 2006-09-22 13:01:10 EDT
Have we seen this one again? If not, can we close this one out?
Comment 5 Henry Harris 2006-09-22 15:23:49 EDT
Have not seen this in a long time.  Feel free to close as invalid.
Comment 6 Kiersten (Kerri) Anderson 2006-09-22 15:37:26 EDT
Closing as invalid, feel free to reopen the defect if it should occur again.

Note You need to log in before you can comment on or make changes to this bug.