<div dir="ltr"><div>This error is thrown when i try to create master resource.</div><div><br></div><div>[root@vsanqa11 kiran]# pcs resource master ms-f3611cc5-a68f-4c69-ab35-a9b226473e5d vha-f3611cc5-a68f-4c69-ab35-a9b226473e5d meta clone-max=2 globally-unique=false target-role=started</div>
<div>Error: unable to locate command: /usr/sbin/cibadmin</div><div>[root@vsanqa11 kiran]# pcs resource master ms-f3611cc5-a68f-4c69-ab35-a9b226473e5d vha-f3611cc5-a68f-4c69-ab35-a9b226473e5d meta clone-max=2 globally-unique=false target-role=started</div>
<div>Error: unable to locate command: /usr/sbin/cibadmin</div><div>[root@vsanqa11 kiran]# pcs resource master ms-f3611cc5-a68f-4c69-ab35-a9b226473e5d vha-f3611cc5-a68f-4c69-ab35-a9b226473e5d meta clone-max=2 globally-unique=false target-role=started</div>
<div>Error: unable to locate command: /usr/sbin/cibadmin</div><div>[root@vsanqa11 kiran]# pcs resource master ms-f3611cc5-a68f-4c69-ab35-a9b226473e5d vha-f3611cc5-a68f-4c69-ab35-a9b226473e5d meta clone-max=2 globally-unique=false target-role=started</div>
<div>Error: unable to locate command: /usr/sbin/cibadmin</div><div>[root@vsanqa11 kiran]# pcs resource master ms-f3611cc5-a68f-4c69-ab35-a9b226473e5d vha-f3611cc5-a68f-4c69-ab35-a9b226473e5d meta clone-max=2 globally-unique=false target-role=started</div>
<div>Error: unable to locate command: /usr/sbin/cibadmin</div><div>[root@vsanqa11 kiran]# pcs status | grep "vha-f3611cc5-a68f-4c69-ab35-a9b226473e5d"</div><div> vha-f3611cc5-a68f-4c69-ab35-a9b226473e5d (ocf::heartbeat:vgc-cm-agent.ocf): Started vsanqa11</div>
<div>[root@vsanqa11 kiran]# pcs resource master ms-f3611cc5-a68f-4c69-ab35-a9b226473e5d vha-f3611cc5-a68f-4c69-ab35-a9b226473e5d meta clone-max=2 globally-unique=false target-role=started</div><div>Error: unable to locate command: /usr/sbin/cibadmin</div>
<div><br></div><div><br></div><div><br></div><div>Creation of these resources is automated using a script. Here is snippet of the script:</div><div><br></div><div><div> pcs cluster cib $CLUSTER_CREATE_LOG || exit 1</div>
<div><br></div><div> pcs -f $CLUSTER_CREATE_LOG property set stonith-enabled=false || exit 1</div><div> pcs -f $CLUSTER_CREATE_LOG property set no-quorum-policy=ignore || exit 1</div><div> #syntax for following command is different across pcs 9.26 and 9.90</div>
<div> pcs -f $CLUSTER_CREATE_LOG resource defaults resource-stickiness=100 > /dev/null 2>&1</div><div> if [ $? -ne 0 ]; then</div><div> pcs -f $CLUSTER_CREATE_LOG resource rsc defaults resource-stickiness=100 || exit 1</div>
<div> fi</div><div> pcs -f $CLUSTER_CREATE_LOG resource create vha-$uuid ocf:heartbeat:vgc-cm-agent.ocf\</div><div> cluster_uuid=$uuid \</div><div> op monitor role="Master" interval=30s timeout=100s\</div>
<div> op monitor role="Slave" interval=31s timeout=100s || exit 1</div><div> pcs -f $CLUSTER_CREATE_LOG resource master ms-${uuid} vha-${uuid} meta clone-max=2 \</div><div> globally-unique=false target-role=started || exit 1</div>
<div><br></div><div> pcs -f $CLUSTER_CREATE_LOG constraint location vha-${uuid} prefers $node1 || exit 1</div><div> pcs -f $CLUSTER_CREATE_LOG constraint location vha-${uuid} prefers $node2 || exit 1</div>
<div> pcs -f $CLUSTER_CREATE_LOG constraint location ms-${uuid} prefers $node1 || exit 1</div><div> pcs -f $CLUSTER_CREATE_LOG constraint location ms-${uuid} prefers $node2 || exit 1</div><div><br></div>
<div> #syntax for following command is different across pcs 9.26 and 9.90</div><div> pcs cluster cib-push $CLUSTER_CREATE_LOG > /dev/null 2>&1</div><div> if [ $? -ne 0 ]; then</div><div> pcs cluster push cib $CLUSTER_CREATE_LOG</div>
<div> fi</div></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 21, 2014 at 3:52 PM, Andrew Beekhof <span dir="ltr"><<a href="mailto:andrew@beekhof.net" target="_blank">andrew@beekhof.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Chris,<br>
<br>
Does the error below mean anything to you?<br>
This seems to be happening once the CIB reaches a certain size, but is on the client side and possibly before the pacemaker tools are invoked.<br>
<div class=""><br>
On 9 Jul 2014, at 6:49 pm, K Mehta <<a href="mailto:kiranmehta1981@gmail.com">kiranmehta1981@gmail.com</a>> wrote:<br>
<br>
</div><div class="">> [root@vsanqa11 ~]# pcs resource create vha-3de5ab16-9917-4b90-93d2-7b04fc71879c ocf:heartbeat:vgc-cm-agent.ocf cluster_uuid=3de5ab16-9917-4b90-93d2-7b04fc71879c op monitor role="Master" interval=30s timeout=100s op monitor role="Master" interval=30s timeout=100s<br>
><br>
><br>
> pcs status output includes<br>
> vha-3de5ab16-9917-4b90-93d2-7b04fc71879c (ocf::heartbeat:vgc-cm-agent.ocf): Started vsanqa11<br>
><br>
><br>
> [root@vsanqa11 ~]# pcs resource master ms-3de5ab16-9917-4b90-93d2-7b04fc71879c vha-3de5ab16-9917-4b90-93d2-7b04fc71879c meta clone-max=2 globally-unique=false target-role=started<br>
> Error: unable to locate command: /usr/sbin/cibadmin<br>
><br>
<br>
<br>
</div>Looking in the logs, I see:<br>
<br>
Jul 12 11:18:24 vsanqa11 cibadmin[7966]: notice: crm_log_args: Invoked: /usr/sbin/cibadmin -c -R --xml-text <crm_config>#012 <cluster_property_set id="cib-bootstrap-options">#012 <nvpair id="cib-bootstrap-options-dc-version" name="dc-version" value="1.1.10-14.el6_5.2-368c726"/>#012 <nvpair id="cib-bootstrap-options-cluster-infrastructure" name="cluster-infrastructure" value="cman"/>#012 #012 <nvpair id="cib-bootstrap-options-no-quorum-policy" name="no-quorum-policy" value="ignore"/>#012 <nvpair id="cib-bootstrap-options-stonith-enabled" name="stoni<br>
<br>
But am I right in thinking that this that doesn't look like the result of a pcs command?<br>
<br>
Kiran: Can you give us more information on the other commands you're running?<br>
</blockquote></div><br></div>