[Pacemaker] Unable to configure Pacemaker with cibadmin

[Andrew Beekhof]

On Sat, Jul 23, 2011 at 11:57 AM, Kelly Wong <kellwong at cisco.com> wrote:
> Hello,
>
> I am trying to update the configuration of my cluster through the cibadmin
> command, but the command always fails:
>
> cibadmin --replace --scope resources --xml-file r.xml
> Call cib_replace failed (-41): Remote node did not respond

That error is triggered by a timeout.  How long does the command wait
before returning this error?

> <null>
>
> I was able to replace the initial blank configuration, but updating it
> doesn’t seem to work.  The cluster is functioning and running some of the
> resources.  Some of the are down, but I don’t think that should make a
> difference:
>
> ============
> Last updated: Fri Jul 22 18:33:03 2011
> Stack: openais
> Current DC: poc-tst-rh4 - partition with quorum
> Version: 1.0.9-89bd754939df5150de7cd76835f98fe90851b677
> 2 Nodes configured, 2 expected votes
> 3 Resources configured.
> ============
>
> Online: [ poc-tst-rh4 poc-tst-rh4-2 ]
>
>  Resource Group: mysql
>      fs_mysql    (ocf::heartbeat:Filesystem):    Started poc-tst-rh4
>      mysqld    (ocf::heartbeat:mysql):    Stopped
>  Master/Slave Set: ms_drbd_mysql
>      Masters: [ poc-tst-rh4 ]
>      Slaves: [ poc-tst-rh4-2 ]
>  Clone Set: pingclone
>      Started: [ poc-tst-rh4-2 poc-tst-rh4 ]
>
> Failed actions:
>     mysqld_start_0 (node=poc-tst-rh4, call=26, rc=5, status=complete): not
> installed
>     fs_mysql_start_0 (node=poc-tst-rh4-2, call=31, rc=5, status=complete):
> not installed
>
> If I try to use the crm command line, it rejects any configuration changes I
> make:
> crm configure edit
> ERROR: could not replace mysql
> INFO: offending xml: <group id="mysql">
>     <meta_attributes id="mysql-meta_attributes">
>         <nvpair id="mysql-meta_attributes-target-role" name="target-role"
> value="Started"/>
>     </meta_attributes>
>     <primitive class="ocf" id="fs_mysql" provider="heartbeat"
> type="Filesystem">
>         <instance_attributes id="fs_mysql-instance_attributes">
>             <nvpair id="fs_mysql-instance_attributes-device" name="device"
> value="/dev/drbd0"/>
>             <nvpair id="fs_mysql-instance_attributes-directory"
> name="directory" value="/var/lib/mysql/"/>
>             <nvpair id="fs_mysql-instance_attributes-fstype" name="fstype"
> value="ext3"/>
>         </instance_attributes>
>         <operations>
>             <op id="fs_mysql-start-0" interval="0" name="start"
> timeout="60"/>
>             <op id="fs_mysql-stop-0" interval="0" name="stop" timeout="60"/>
>         </operations>
>     </primitive>
>     <primitive class="ocf" id="mysqld" provider="heartbeat" type="mysql">
>         <instance_attributes id="mysqld-instance_attributes">
>             <nvpair id="mysqld-instance_attributes-binary" name="binary"
> value="/usr/bin/mysqld_safe"/>
>             <nvpair id="mysqld-instance_attributes-pid" name="pid"
> value="/var/lib/mysql/mysql.pid"/>
>         </instance_attributes>
>         <operations>
>             <op id="mysqld-monitor-15s" interval="15s" name="monitor"
> timeout="60"/>
>             <op id="mysqld-start-0" interval="0" name="start"
> timeout="240"/>
>             <op id="mysqld-stop-0" interval="0" name="stop" timeout="240"/>
>         </operations>
>     </primitive>
> </group>
>
>
> What could be causing the configuration to fail?
>
> Thank you for any assistance,
> Kelly Wong
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
>