<div dir="ltr">I suppose the failure is because I do not have a DC yet.<div><br></div><div><div>[root@airv_cu xml]# pcs cluster status</div><div>Cluster Status:</div><div> Stack: corosync</div><div> Current DC: NONE</div></div><div><br></div><div>Can I bring it up when I have just 1 node?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 6, 2016 at 4:59 PM, Nikhil Utane <span dir="ltr"><<a href="mailto:nikhil.subscribed@gmail.com" target="_blank">nikhil.subscribed@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>The command failed. </div><div>[root@airv_cu pacemaker]# cibadmin --upgrade --force</div><div>Call cib_upgrade failed (-62): Timer expired</div></div><div><br></div>I did not do any tooling. (Not even aware how to)<div><br></div><div>As I mentioned, I am cross-compiling and copying the relevant files on target platform.</div><div>In one of the earlier run pacemaker cribbed out not finding <span style="font-family:Calibri,sans-serif;font-size:11pt">/usr/share/pacemaker/</span>pacemaker-1.0.rng.</div><div><br></div><div>I found this file under xml folder in the build folder, so I copied all the files under xml folder onto the target.</div><div>Did that screw it up?</div><div><br></div><div>This is the content of the folder:</div><div><div>[root@airv_cu pacemaker]# ls /usr/share/pacemaker/</div><div>Makefile constraints-2.1.rng nodes-1.0.rng pacemaker-2.1.rng rule.rng</div><div>Makefile.am constraints-2.2.rng nodes-1.2.rng pacemaker-2.2.rng score.rng</div><div>Makefile.in constraints-2.3.rng nodes-1.3.rng pacemaker-2.3.rng status-1.0.rng</div><div>Readme.md constraints-next.rng nvset-1.3.rng pacemaker-2.4.rng tags-1.3.rng</div><div>acls-1.2.rng context-of.xsl nvset.rng pacemaker-next.rng upgrade-1.3.xsl</div><div>acls-2.0.rng crm-transitional.dtd ocf-meta2man.xsl pacemaker.rng upgrade06.xsl</div><div>best-match.sh crm.dtd options-1.0.rng <a href="http://regression.core.sh" target="_blank">regression.core.sh</a> versions.rng</div><div>cib-1.0.rng crm.xsl pacemaker-1.0.rng regression.sh</div><div>cib-1.2.rng crm_mon.rng pacemaker-1.2.rng resources-1.0.rng</div><div>constraints-1.0.rng fencing-1.2.rng pacemaker-1.3.rng resources-1.2.rng</div><div>constraints-1.2.rng fencing-2.4.rng pacemaker-2.0.rng resources-1.3.rng</div></div><div><br></div><div>-Regards</div><span class="HOEnZb"><font color="#888888"><div>Nikhil</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 6, 2016 at 4:41 PM, Klaus Wenninger <span dir="ltr"><<a href="mailto:kwenning@redhat.com" target="_blank">kwenning@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>On 05/06/2016 12:40 PM, Nikhil Utane wrote:<br>
> Hi,<br>
><br>
> I used the blackbox feature which showed the reason for failure.<br>
> As I am cross-compiling pacemaker on a build machine and later moving<br>
> the binaries to the target, few binaries were missing. After fixing<br>
> that and bunch of other errors/warning, I am able to get pacemaker<br>
> started though not completely running fine.<br>
><br>
> The node is not getting added:<br>
> airv_cu cib: error: xml_log:Element node failed to validate<br>
> attributes<br>
><br>
> I suppose it is because of this error:<br>
> crmd: error: node_list_update_callback:Node update 4 failed: Update<br>
> does not conform to the configured schema (-203)<br>
><br>
> I am suspecting this is caused because of<br>
> validate-with="pacemaker-0.7" in the cib. In another installation this<br>
> is being set to '"pacemaker-2.0"'<br>
><br>
> [root@airv_cu pacemaker]# pcs cluster cib<br>
> <cib crm_feature_set="3.0.10" validate-with="pacemaker-0.7" epoch="3"<br>
> num_updates="0" admin_epoch="0" cib-last-written="Fri May 6 09:28:10<br>
> 2016" have-quorum="1"><br>
> <configuration><br>
> <crm_config><br>
> <cluster_property_set id="cib-bootstrap-options"><br>
> <nvpair id="cib-bootstrap-options-have-watchdog"<br>
> name="have-watchdog" value="true"/><br>
> <nvpair id="cib-bootstrap-options-dc-version"<br>
> name="dc-version" value="1.1.14-5a6cdd1"/><br>
> <nvpair id="cib-bootstrap-options-cluster-infrastructure"<br>
> name="cluster-infrastructure" value="corosync"/><br>
> </cluster_property_set><br>
> </crm_config><br>
> <nodes/><br>
> <resources/><br>
> <constraints/><br>
> </configuration><br>
> <status/><br>
> </cib><br>
><br>
> Any idea why/where this is being set to 0.7. I am using latest<br>
> pacemaker from GitHub.<br>
<br>
</div></div>What kind of tooling did you use to create the cib?<br>
Try 'cibadmin --upgrade'. That should set the cib-version to what your<br>
pacemaker-version supports.<br>
<span><br>
><br>
> [root@airv_cu pacemaker]# pacemakerd --version<br>
> Pacemaker 1.1.14<br>
> Written by Andrew Beekhof<br>
><br>
> Attaching the corosync.log and corosync.conf file.<br>
><br>
> -Thanks<br>
> Nikhil<br>
><br>
><br>
> On Thu, May 5, 2016 at 10:21 PM, Ken Gaillot <<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a><br>
</span><div><div>> <mailto:<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a>>> wrote:<br>
><br>
> On 05/05/2016 11:25 AM, Nikhil Utane wrote:<br>
> > Thanks Ken for your quick response as always.<br>
> ><br>
> > But what if I don't want to use quorum? I just want to bring up<br>
> > pacemaker + corosync on 1 node to check that it all comes up fine.<br>
> > I added corosync_votequorum as you suggested. Additionally I<br>
> also added<br>
> > these 2 lines:<br>
> ><br>
> > expected_votes: 2<br>
> > two_node: 1<br>
><br>
> There's actually nothing wrong with configuring a single-node cluster.<br>
> You can list just one node in corosync.conf and leave off the above.<br>
><br>
> > However still pacemaker is not able to run.<br>
><br>
> There must be other issues involved. Even if pacemaker doesn't have<br>
> quorum, it will still run, it just won't start resources.<br>
><br>
> > [root@airv_cu root]# pcs cluster start<br>
> > Starting Cluster...<br>
> > Starting Pacemaker Cluster Manager[FAILED]<br>
> ><br>
> > Error: unable to start pacemaker<br>
> ><br>
> > Corosync.log:<br>
> > *May 05 16:15:20 [16294] airv_cu pacemakerd: info:<br>
> > pcmk_quorum_notification: Membership 240: quorum still lost (1)*<br>
> > May 05 16:15:20 [16259] airv_cu corosync debug [QB ] Free'ing<br>
> > ringbuffer: /dev/shm/qb-cmap-request-16259-16294-21-header<br>
> > May 05 16:15:20 [16294] airv_cu pacemakerd: notice:<br>
> > crm_update_peer_state_iter: pcmk_quorum_notification: Node<br>
> > airv_cu[181344357] - state is now member (was (null))<br>
> > May 05 16:15:20 [16294] airv_cu pacemakerd: info:<br>
> > pcmk_cpg_membership: Node 181344357 joined group pacemakerd<br>
> > (counter=0.0)<br>
> > May 05 16:15:20 [16294] airv_cu pacemakerd: info:<br>
> > pcmk_cpg_membership: Node 181344357 still member of group<br>
> > pacemakerd (peer=airv_cu, counter=0.0)<br>
> > May 05 16:15:20 [16294] airv_cu pacemakerd: warning:<br>
> pcmk_child_exit:<br>
> > The cib process (16353) can no longer be respawned, shutting the<br>
> > cluster down.<br>
> > May 05 16:15:20 [16294] airv_cu pacemakerd: notice:<br>
> > pcmk_shutdown_worker: Shutting down Pacemaker<br>
> ><br>
> > The log and conf file is attached.<br>
> ><br>
> > -Regards<br>
> > Nikhil<br>
> ><br>
> > On Thu, May 5, 2016 at 8:04 PM, Ken Gaillot <<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a><br>
> <mailto:<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a>><br>
</div></div><div><div>> > <mailto:<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a> <mailto:<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a>>>> wrote:<br>
> ><br>
> > On 05/05/2016 08:36 AM, Nikhil Utane wrote:<br>
> > > Hi,<br>
> > ><br>
> > > Continuing with my adventure to run Pacemaker & Corosync<br>
> on our<br>
> > > big-endian system, I managed to get past the corosync<br>
> issue for now. But<br>
> > > facing an issue in running Pacemaker.<br>
> > ><br>
> > > Seeing following messages in corosync.log.<br>
> > > pacemakerd: warning: pcmk_child_exit: The cib process<br>
> (20000) can no<br>
> > > longer be respawned, shutting the cluster down.<br>
> > > pacemakerd: warning: pcmk_child_exit: The stonith-ng<br>
> process (20001)<br>
> > > can no longer be respawned, shutting the cluster down.<br>
> > > pacemakerd: warning: pcmk_child_exit: The lrmd process<br>
> (20002) can no<br>
> > > longer be respawned, shutting the cluster down.<br>
> > > pacemakerd: warning: pcmk_child_exit: The attrd process<br>
> (20003) can<br>
> > > no longer be respawned, shutting the cluster down.<br>
> > > pacemakerd: warning: pcmk_child_exit: The pengine<br>
> process (20004) can<br>
> > > no longer be respawned, shutting the cluster down.<br>
> > > pacemakerd: warning: pcmk_child_exit: The crmd process<br>
> (20005) can no<br>
> > > longer be respawned, shutting the cluster down.<br>
> > ><br>
> > > I see following error before these messages. Not sure if<br>
> this is the cause.<br>
> > > May 05 11:26:24 [19998] airv_cu pacemakerd: error:<br>
> > > cluster_connect_quorum: Corosync quorum is not configured<br>
> > ><br>
> > > I tried removing the quorum block (which is anyways blank)<br>
> from the conf<br>
> > > file but still had the same error.<br>
> ><br>
> > Yes, that is the issue. Pacemaker can't do anything if it<br>
> can't ask<br>
> > corosync about quorum. I don't know what the issue is at the<br>
> corosync<br>
> > level, but your corosync.conf should have:<br>
> ><br>
> > quorum {<br>
> > provider: corosync_votequorum<br>
> > }<br>
> ><br>
> ><br>
> > > Attaching the log and conf files. Please let me know if<br>
> there is any<br>
> > > obvious mistake or how to investigate it further.<br>
> > ><br>
> > > I am using pcs cluster start command to start the cluster<br>
> > ><br>
> > > -Thanks<br>
> > > Nikhil<br>
><br>
><br>
><br>
><br>
</div></div><div><div>> _______________________________________________<br>
> Users mailing list: <a href="mailto:Users@clusterlabs.org" target="_blank">Users@clusterlabs.org</a><br>
> <a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/mailman/listinfo/users</a><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
<br>
_______________________________________________<br>
Users mailing list: <a href="mailto:Users@clusterlabs.org" target="_blank">Users@clusterlabs.org</a><br>
<a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/mailman/listinfo/users</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>