Following command was failing 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
So i did the following 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 --debug > xmlfile #removed first three lines which are not part of xml from the xmlfile generated cibadmin -Mc --xml-file=xmlfile But pcs status did not show the resource for which pcs resource command had failed Also tried cibadmin --R --xml-file=xmlfile But even then didnt find the resource in output of pcs status 1. Are these right set of commands ? 2. Which version of pcs has fix for this issue ? regards, kiran On Mon, Jul 21, 2014 at 10:21 PM, Colin Mason <cma...@frontiernetworks.ca> wrote: > Yes, I had 10 (20) Master/Slave resources, 5 (10) clone resources, 24 > simple resources for a total of 54 when I started running into this error. > I could not create another Master/Slave resource with the exact same error. > > > > Error: unable to locate command: /usr/sbin/cibadmin > > > > You are simply hitting a limit of the amount of characters you can use on > one command because cib.xml is getting large. Use pcs --debug to dump the > XML to screen, paste it into a file and run cibadmin --xml-file directly > for a workaround. Works great. > > > > Colin > > > > > > *From:* K Mehta [mailto:kiranmehta1...@gmail.com] > *Sent:* Monday, July 21, 2014 12:28 PM > *To:* Colin Mason > > *Subject:* Re: [Pacemaker] Cannot create more than 27 multistate resources > > > > Colin, > > In your setup do you have multi state resources or simple > resources ? > > In my case, I get error in creation of master after successful > creation of 27 multi state resources. > > > > [root@vsanqa11 kiran]# pcs status > > Cluster name: vsanqa11_12 > > Last updated: Mon Jul 21 09:25:36 2014 > > Last change: Mon Jul 21 09:17:25 2014 via cibadmin on vsanqa11 > > Stack: cman > > Current DC: vsanqa12 - partition with quorum > > Version: 1.1.10-14.el6_5.2-368c726 > > 2 Nodes configured > > 55 Resources configured **<<<<< (27 multi state resources on two node > cluster = 54 resources + 1 resource whose master is to be created) > > > > After this master resource cannot be created. > > > > > > > > On Mon, Jul 21, 2014 at 8:51 PM, Colin Mason <cma...@frontiernetworks.ca> > wrote: > > I have run into this issue with greater than 55 resources when using > pcs-0.9.90-2.el6.centos.2.noarch. > > The other workaround is to run the pcs command with --debug. Take the > whole XML text that pcs is trying to run cibadmin with and place it into a > text file. Now convert the cibadmin command from --xml-text (-X) to > --xml-file (-x) and use the XML file you just created. Fixed. > > Colin > > > -----Original Message----- > From: Chris Feist [mailto:cfe...@redhat.com] > Sent: Monday, July 21, 2014 11:14 AM > To: K Mehta > Cc: The Pacemaker cluster resource manager > Subject: Re: [Pacemaker] Cannot create more than 27 multistate resources > > On 07/21/2014 05:22 AM, Andrew Beekhof 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. > > I grabbed your debug file and did some tests and it looks like the issue > is caused by earlier version of pcs (0.9.90 is affected) which try to pass > the entire cib on the command line to cibadmin. This has been fixed > upstream (and should be built in the next release of RHEL/CentOS). > > As a workaround, you can use the upstream sources here: > https://github.com/feist/pcs (just run pcs from the directory that is > cloned). > > Thanks! > Chris > > > > > 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 > > >
_______________________________________________ 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
