pacemaker service fails to start and/or nodes are unable to join the cluster while logs show no errors or output from pacemaker daemons in a RHEL 6 Update 7 High Availability cluster
Issue
- I updated to RHEL 6.7 and tried to restart my cluster, but
pacemakerfails to start. There is nothing logged by any of thepacemakerdaemons when this happens. - Newly installed cluster nodes fails to join the cluster and
pacemakerservice will fail to start manually. pacemakerwon't start after I updated it to the release from RHEL 6 Update 7- I updated the packages on my nodes and now my nodes can't join the cluster together
- Two nodes do not join each other to form the cluster and manually starting
pacemakerservice fails.
# service pacemaker 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... [ OK ]
Starting fenced... [ OK ]
Starting dlm_controld... [ OK ]
Tuning DLM kernel config... [ OK ]
Starting gfs_controld... [ OK ]
Unfencing self... [ OK ]
Joining fence domain... [ OK ]
Starting Pacemaker Cluster Manager [FAILED]
# pcs cluster start
Starting Cluster...
Starting Pacemaker Cluster Manager [FAILED]
Error: unable to start pacemaker
Environment
- Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
pacemaker-1.1.12-8.el6or laterlibqb-0.16.0-2.el6or earlier
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.