On 25/08/15 14:14, Streeter, Michelle N wrote:
I am using pcs but it does nothing with the cluster.conf file. Also, I am
currently required to use rhel6.6.
I have not been able to find any documentation on what is required in the
cluster.conf file under the newer versions of pacemaker and I have not been
able to reduce my current version down enough to satisfy pacemaker and so
would you please provide an example of what is required in the cluster.conf
file?
I don't think CMAN component can operate without that file (location
possibly overridden with $COROSYNC_CLUSTER_CONFIG_FILE environment
variable). What distro, or at least commands to bring the cluster up
do you use?
We are only allowed to download from Red hat and I have both corosync and
pacemaker services set to on so they start at boot up. It does not matter
if I stop all three services cman, corosync, and pacemaker and then start
corosync first and then pacemaker, if I have a cluster.conf file in place, it
fails to start.
We need to know more about what exactly you mean by 'failed to start'.
Actual error messages and the command you used to start the cluster
would be appreciated, along with any syslog messages.
pacemaker on RHEL-6 requires cman. if cman is failing to start then
that's a configuration error that we need to look into (and that
cluster.conf you posted is not enough for a valid cluster BTW - you need
fencing in there at least!).
If the cluster starts 'without cman' then I can only assume that
something is very strangely wrong on your system. What command do you
use in this scenario, and what do you class as 'started'? Again
messages, and logs would be helpful in diagnosing what's going on here,
Chrissie
This is my current cluster.conf file which just failed.
?xml version=1.0?
cluster name=CNAS
clusternodes
clusternode name=nas01
/clusternode
clusternode name=nas02
/clusternode
/clusternodes
/cluster
Michelle Streeter
ASC2 MCS - SDE/ACL/SDL/EDL OKC Software Engineer
The Boeing Company
Date: Mon, 24 Aug 2015 17:52:01 +
From: Streeter, Michelle N michelle.n.stree...@boeing.com
To: users@clusterlabs.org users@clusterlabs.org
Subject: [ClusterLabs] Cluster.conf
Message-ID:
9a18847a77a9a14da7e0fd240efcafc2504...@xch-phx-501.sw.nos.boeing.com
Content-Type: text/plain; charset=us-ascii
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
-- next part --
An HTML attachment was scrubbed...
URL:
http://clusterlabs.org/pipermail/users/attachments/20150824/f7abecda/attachment-0001.html
--
Message: 3
Date: Mon, 24 Aug 2015 14:00:48 -0400
From: Digimer li...@alteeve.ca
To: Cluster Labs - All topics related to open-source clustering
welcomedusers@clusterlabs.org
Subject: Re: [ClusterLabs] Cluster.conf
Message-ID: 55db5bd0.4010...@alteeve.ca
Content-Type: text/plain; charset=windows-1252
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
___
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
___
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
