This error is thrown when i try to create master resource.
[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
Error: unable to locate command: /usr/sbin/cibadmin
[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
Error: unable to locate command: /usr/sbin/cibadmin
[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
Error: unable to locate command: /usr/sbin/cibadmin
[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
Error: unable to locate command: /usr/sbin/cibadmin
[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
Error: unable to locate command: /usr/sbin/cibadmin
[root@vsanqa11 kiran]# pcs status | grep
"vha-f3611cc5-a68f-4c69-ab35-a9b226473e5d"
vha-f3611cc5-a68f-4c69-ab35-a9b226473e5d
(ocf::heartbeat:vgc-cm-agent.ocf): Started vsanqa11
[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
Error: unable to locate command: /usr/sbin/cibadmin
Creation of these resources is automated using a script. Here is snippet of
the script:
pcs cluster cib $CLUSTER_CREATE_LOG || exit 1
pcs -f $CLUSTER_CREATE_LOG property set stonith-enabled=false ||
exit 1
pcs -f $CLUSTER_CREATE_LOG property set no-quorum-policy=ignore ||
exit 1
#syntax for following command is different across pcs 9.26 and 9.90
pcs -f $CLUSTER_CREATE_LOG resource defaults
resource-stickiness=100 > /dev/null 2>&1
if [ $? -ne 0 ]; then
pcs -f $CLUSTER_CREATE_LOG resource rsc defaults
resource-stickiness=100 || exit 1
fi
pcs -f $CLUSTER_CREATE_LOG resource create vha-$uuid
ocf:heartbeat:vgc-cm-agent.ocf\
cluster_uuid=$uuid \
op monitor role="Master" interval=30s timeout=100s\
op monitor role="Slave" interval=31s timeout=100s || exit 1
pcs -f $CLUSTER_CREATE_LOG resource master ms-${uuid} vha-${uuid}
meta clone-max=2 \
globally-unique=false target-role=started || exit 1
pcs -f $CLUSTER_CREATE_LOG constraint location vha-${uuid}
prefers $node1 || exit 1
pcs -f $CLUSTER_CREATE_LOG constraint location vha-${uuid}
prefers $node2 || exit 1
pcs -f $CLUSTER_CREATE_LOG constraint location ms-${uuid} prefers
$node1 || exit 1
pcs -f $CLUSTER_CREATE_LOG constraint location ms-${uuid} prefers
$node2 || exit 1
#syntax for following command is different across pcs 9.26 and 9.90
pcs cluster cib-push $CLUSTER_CREATE_LOG > /dev/null 2>&1
if [ $? -ne 0 ]; then
pcs cluster push cib $CLUSTER_CREATE_LOG
fi
On Mon, Jul 21, 2014 at 3:52 PM, Andrew Beekhof <and...@beekhof.net> wrote:
> Chris,
>
> Does the error below mean anything to you?
> 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.
>
> On 9 Jul 2014, at 6:49 pm, K Mehta <kiranmehta1...@gmail.com> wrote:
>
> > [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
> >
> >
> > pcs status output includes
> > vha-3de5ab16-9917-4b90-93d2-7b04fc71879c
> (ocf::heartbeat:vgc-cm-agent.ocf): Started vsanqa11
> >
> >
> > [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
> > Error: unable to locate command: /usr/sbin/cibadmin
> >
>
>
> Looking in the logs, I see:
>
> 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
>
> But am I right in thinking that this that doesn't look like the result of
> a pcs command?
>
> Kiran: Can you give us more information on the other commands you're
> running?
>
_______________________________________________
Pacemaker mailing list: Pacemaker@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
