CMAN fails to start with "Waiting for quorum... Timed-out waiting for cluster" after removing a quorum device from the configuration in RHEL 6
Issue
-
Per recommendation I have eliminated a Quorum disk from my two node High Availability cluster. Currently when I boot up a single node, the file system does not mount automatically. Not sure what's going on at this point?
-
Attempting to manually start the
cmanservice fails with:
[root@node1 ~]# service cman start
Starting cluster:
Checking if cluster has been disabled at boot... [ OK ]
Checking Network Manager... [ OK ]
Global setup... [ OK ]
Loading kernel modules... [ OK ]
Mounting configfs... [ OK ]
Starting cman... [ OK ]
Waiting for quorum... Timed-out waiting for cluster
[FAILED]
Stopping cluster:
Leaving fence domain... [ OK ]
Stopping gfs_controld... [ OK ]
Stopping dlm_controld... [ OK ]
Stopping fenced... [ OK ]
Stopping cman... [ OK ]
Waiting for corosync to shutdown: [ OK ]
Unloading kernel modules... [ OK ]
Unmounting configfs... [ OK ]
Environment
- Red Hat Enterprise Linux(RHEL) 6 with the High Availability Add On
expected_votesset higher than the number of node votes present in the cluster- NO quorum device configured in the cluster (
<quorumd>is unset in/etc/cluster/cluster.conf)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
