<div dir="ltr"><div><div><div><div><div>Dear All,<br><br></div>I m trying to use pacemaker and corosync for the clustering requirement that came up recently.<br>We have cross compiled corosync, pacemaker and pcs(python) for ppc environment (Target board where pacemaker and corosync are supposed
to run)<br>I m having trouble bringing up pacemaker in that environment, though I could successfully bring up corosync.<br></div><div>Any help is welcome.<br></div><br></div><div>I m using these versions of pacemaker and corosync<br>[root@node_cu pacemaker]# corosync -v<br><b>Corosync Cluster Engine, version '2.3.5'</b><br>Copyright (c) 2006-2009 Red Hat, Inc.<br>[root@node_cu pacemaker]# pacemakerd -$<br><b>Pacemaker 1.1.14<br>Written by Andrew Beekhof</b><br><br></div>For running corosync, I did the following.<br></div>1. Created the following directories,<br> /var/lib/pacemaker<br></div><div> /var/lib/corosync<br> /var/lib/pacemaker<br> /var/lib/pacemaker/cores<br> /var/lib/pacemaker/pengine<br> /var/lib/pacemaker/blackbox<br> /var/lib/pacemaker/cib<br> <br> </div>2. Created a file called corosync.conf under /etc/corosync folder with the following contents<br><br>totem {<br><br> version: 2<br> token: 5000<br> token_retransmits_before_loss_const: 20<br> join: 1000<br> consensus: 7500<br> vsftype: none<br> max_messages: 20<br> secauth: off<br> cluster_name: mycluster<br> transport: udpu<br> threads: 0<br> clear_node_high_bit: yes<br><br> interface {<br> ringnumber: 0<br> # The following three values need to be set based on your environment<br> bindnetaddr: 10.x.x.x<br> mcastaddr: 226.94.1.1<br> mcastport: 5405<br> }<br> }<br><br> logging {<br> fileline: off<br> to_syslog: yes<br> to_stderr: no<br> to_syslog: yes<br> logfile: /var/log/corosync.log<br> syslog_facility: daemon<br> debug: on<br> timestamp: on<br> }<br><br> amf {<br> mode: disabled<br> }<br><br> quorum {<br> provider: corosync_votequorum<br> }<br><br>nodelist {<br> node {<br> ring0_addr: node_cu<br> nodeid: 1<br> }<br>}<br><br><div><div><div>3. Created authkey under /etc/corosync<br></div><div><br>4. Created a file called pcmk under /etc/corosync/service.d and contents as below,<br></div><div> cat pcmk<br> service {<br> # Load the Pacemaker Cluster Resource Manager<br> name: pacemaker<br> ver: 1<br> }<br><br></div><div>5. Added the node name "node_cu" in /etc/hosts with 10.X.X.X ip <br><br></div><div>6. ./corosync -f -p & --> this step started corosync<br><br>[root@node_cu pacemaker]# netstat -alpn | grep -i coros<br>udp 0 0 10.X.X.X:61841 0.0.0.0:* 9133/corosync<br>udp 0 0 10.X.X.X:5405 0.0.0.0:* 9133/corosync<br>unix 2 [ ACC ] STREAM LISTENING 148888 9133/corosync @quorum<br>unix 2 [ ACC ] STREAM LISTENING 148884 9133/corosync @cmap<br>unix 2 [ ACC ] STREAM LISTENING 148887 9133/corosync @votequorum<br>unix 2 [ ACC ] STREAM LISTENING 148885 9133/corosync @cfg<br>unix 2 [ ACC ] STREAM LISTENING 148886 9133/corosync @cpg<br>unix 2 [ ] DGRAM 148840 9133/corosync<br><br></div><div>7. ./pacemakerd -f & gives the following error and exits.<br>[root@node_cu pacemaker]# pacemakerd -f<br>cmap connection setup failed: CS_ERR_TRY_AGAIN. Retrying in 1s<br>cmap connection setup failed: CS_ERR_TRY_AGAIN. Retrying in 2s<br>cmap connection setup failed: CS_ERR_TRY_AGAIN. Retrying in 3s<br>cmap connection setup failed: CS_ERR_TRY_AGAIN. Retrying in 4s<br>cmap connection setup failed: CS_ERR_TRY_AGAIN. Retrying in 5s<br>Could not connect to Cluster Configuration Database API, error 6<br><br></div><div>Can you please point me, what is missing in these steps ?<br></div><div><br></div><div>Before trying these steps, I tried running "pcs cluster start", but that command fails with "service" script not found. As the root filesystem doesn't contain either /etc/init.d/ or /sbin/service<br><br></div><div>So, the plan is to bring up corosync and pacemaker manually, later do the cluster configuration using "pcs" commands.<br><br></div><div>Regards,<br></div><div>Sriram<br></div></div></div></div>