The cluster.conf is needed by cman, and in RHEL 6, pacemaker needs to use cman as the quorum provider. So you need a skeleton cluster.conf and it is different from cib.xml.
If you use pcs/pcsd to setup pacemaker on RHEL 6.7, it should configure everything for you, so you should be able to go straight to setting up pacemaker and not worry about cman/corosync directly. digimer On 24/08/15 01:52 PM, Streeter, Michelle N wrote: > If I have a cluster.conf file in /etc/cluster, my cluster will not > start. Pacemaker 1.1.11, Corosync 1.4.7, cman 3.0.12, But if I do not > have a cluster.conf file then my cluster does start with my current > configuration. However, when I try to stop the cluster, it wont stop > unless I have my cluster.conf file in place. How can I dump my cib to > my cluster.conf file so my cluster will start with the conf file in place? > > > > Michelle Streeter > > ASC2 MCS – SDE/ACL/SDL/EDL OKC Software Engineer > The Boeing Company > > > > > > _______________________________________________ > Users mailing list: Users@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? _______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org