Red Hat Bugzilla – Bug 209797
gulm init script will hang if a master is never found.
Last modified: 2009-04-16 16:02:55 EDT
Description of problem:
I had one machine in a cluster come up with the gulm init script on and a valid
cluster.conf file, and it ended up hanging because I never started gulm on any
of the other nodes in the cluster.
Starting ccsd: [ OK ]
[WARNING]lustered mirror log:[WARNING]
It appears that if a master is never found then it will hang. We need to have it
timeout eventually continue booting the node.
stoptime=$(($SECONDS + $GULM_QUORUM_TIMEOUT))
while [ $GULM_QUORUM_TIMEOUT -eq 0 -o $SECONDS -lt $stoptime ]
case $rtrn in
0) break ;; # master was found
1) ;; # master was not found
2) break ;; # gulm_tool error
3) break ;; # we are expired
Version-Release number of selected component (if applicable):
[root@link-08 ~]# rpm -q gulm
I've been unable to replicate this with Corey, moving to NEEDINFO until we see
Have not been able to reproduce this, will reopen if seen again.