Post by Rv RvHello again,
I was able to get the resource started. I noticed that despite executing the
crm configure property stonith-enabled="false" and it returning no erros.
stonith-enabled was not configured. So I edited it by hand.
Now the resource is up but it is not failing over. I will investigate more.
It seems that the guide Clusters from scratch is outdated since there does
not seem to be a need to run pacemaker anymore. Is there any documentation
that is upto date.
Yes, the document you were partially reading.
The old way is to have corosync start the pacemaker daemons.
If you read this carefully, you'll see we specify the new way "ver: 1".
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/s-configure-corosync.html
http://theclusterguy.clusterlabs.org/post/907043024/introducing-the-pacemaker-master-control-process-for
Post by Rv RvElse I will write up something.
Thanks for any inputs
----- Forwarded Message -----
From: Rv Rv <rvrv7575 at yahoo.com>
To: "pacemaker at oss.clusterlabs.org" <pacemaker at oss.clusterlabs.org>
Sent: Tuesday, 22 November 2011 10:47 PM
Subject: Fw: Unable to start pacemaker due to WARN: do_cib_control: Couldn't
complete CIB registration
Thanks for the response. I was trying corosync and pacemaker together though
heartbeat was also installed. Since nothing was working, I created a fresh
fedora install and reinstalled only corosync and pacemaker. I then followed
the guide at http://www.clusterlabs.org/wiki/Install.
This time corosync worked. Pacemaker did not. But it gave an error at
"Nov 22 15:07:31 LVM-2 pacemakerd: [2543]: ERROR: read_config: We can only
start Pacemaker from init if using version 1 of the Pacemaker plugin for
Corosync.? Terminating".
I could not find anything on this. THen I found the blog at
http://blog.hongens.nl/guides/setting-up-a-pacemaker-cluster-on-centosrhel/.
Thankfully just by starting corosync crm resource show stopped giving errors with cib.
So instead of starting pacemaker, I continued with crm_mon.
I executed the commands
crm configure property stonith-enabled="false"
crm configure property no-quorum-policy=ignore
crm configure primitive failover-ip ocf:heartbeat:IPaddr params
ip="10.123.254.213" op monitor interval="2s"
as shown in the blog with the IPaddr changed.
The commands got committed with no issue (except the stonith which is not to
be bothered about right now).
*I still see
[root at LVM-1 corosync]# crm resource show
?failover-ip?(ocf::heartbeat:IPaddr) Stopped
*
How do I start the resource. From /var/log/messages, things seem to be ok.
Config is
root at LVM-1 corosync]# crm configure show
node LVM-1 \
?attributes standby="on"
primitive failover-ip ocf:heartbeat:IPaddr \
?params ip="10.11.19.81" \
?op monitor interval="2s" \
?meta target-role="Started"
property $id="cib-bootstrap-options" \
?dc-version="1.1.6-1.fc14-b379478e0a66af52708f56d0302f50b6f13322bd" \
?cluster-infrastructure="openais" \
?expected-quorum-votes="2" \
?no-quorum-policy="ignore"
I have corosync-1.4.2-1.fc14.x86_64, cluster-glue-1.0.6-1.fc14.x86_64
, pacemaker-1.1.6-1.fc14.x86_64
and heartbeat 3.0.0. installed on my Fedora machines.
I am unable to run commands like
crm resource show
"Error signing on to the CIB service: connection failed"
?WARN: do_cib_control: Couldn't complete CIB registration 16 times... pause and retry
Nov 22 15:15:43 waf1 crmd: [7765]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped (2000ms)
Heartbeat standalone works fine. Corosync starts up fine. Pacemaker fails.
Can someone please help resolve this issue?
Thanks
Post by Rv RvI have corosync-1.4.2-1.fc14.x86_64, cluster-glue-1.0.6-1.fc14.x86_64
, pacemaker-1.1.6-1.fc14.x86_64
and heartbeat 3.0.0. installed on my Fedora machines.
I am unable to run commands like
crm resource show
"Error signing on to the CIB service: connection failed"
?WARN: do_cib_control: Couldn't complete CIB registration 16 times...
pause
and retry
Nov 22 15:15:43 waf1 crmd: [7765]: info: crm_timer_popped: Wait Timer
(I_NULL) just popped (2000ms)
Heartbeat standalone works fine. Corosync starts up fine. Pacemaker fails.
Can someone please help resolve this issue?
Pacemaker is not compiled for Heartbeat in Fedora 16. You can use
Corosync, you can rebuild the Pacemaker, you can choose other distro
or I think you can get packages from some of the HA-companies.
That's about all the options you have.
Rasto
_______________________________________________
Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org