[Linux-HA] heartbeat 2.0.2 problem on two nodes

Andrew Beekhof beekhof at gmail.com
Tue Oct 11 07:19:15 MDT 2005


On 10/11/05, Alberto <xagonzalezm at gmail.com> wrote:
> Hi!
>
>  I am running heartbeat 2.0.2 with this config on two nodes. I start
> heartbeat on node1 and it starts IPaddr resource, but then I start heartbeat
> on node2 and stop node1 and node2 doesnt start resources, it doesnt discover
> failure and cibdamin -Q show a different cib.xml than on node1. Why I dont
> get two nodes synced? If I started node2 with cib.xml empty and it generates
>  an empty one. If I copy node1 cib.xml to node2.xml then I have the IPaddr
> resource up on both nodes!

no logs == no answer possible

it would also be nice to the CIBs from both nodes to see the differences

>
>  Another question is good to have suppress_cib_writes to true, is this just
> for updating and addind uncomplete id fields to xml?

no, it means no changes are ever written to disk

> The problem is that the
> cib.xml get to confused with uids, states, etc. how can this be solved?

the combination of tag name + id must be unique.  if you ensure that
before starting the cluster everything should be fine.

>
>  Thanks!!
>
>  *** ha.cf
>
>  debugfile /var/log/ha/ha.debug
>  logfile /var/log/ha/ha.log
>  node node1
>  node node2
>  keepalive 2
>  deadtime 10
>  ucast eth0 10.64.110.32
>  ping 10.64.110.254
>  auto_failback no
>  crm yes
>  use_logd yes
>  debug 1
>
>
>
>  *** cib.xml:
>
>   <cib generated="true" cib_feature_revision="1" admin_epoch="0" epoch="0"
> num_updates="0" have_quorum="false" last_written="Mon Oct 10 20:04:01 2005">
>     <configuration>
>       <crm_config>
>         <nvpair id="transition_idle_timeout" name="transition_idle_timeout"
> value="120s"/>
>         <nvpair id="symmetric_cluster" name="symmetric_cluster"
> value="true"/>
>         <nvpair id="no_quorum_policy" name="no_quorum_policy" value="stop"/>
>         <nvpair id="suppress_cib_writes" name="suppress_cib_writes"
> value="true"/>
>         <nvpair id="stonith_enabled" name="stonith_enabled" value="false"/>
>         <nvpair id="default_resource_stickiness"
> name="default_resource_stickiness" value="INFINITY"/>
>       </crm_config>
>       <nodes>
>         <node uname="node1" type="member"/>
>         <node uname="node2" type="member"/>
>       </nodes>
>       <resources>
>         <group id="IEL">
>           <primitive class="ocf" id="IEL_IPaddr_70" provider="heartbeat"
> type="IPaddr">
>             <operations>
>               <op id="1" interval="5s" name="monitor" timeout="5s"/>
>             </operations>
>             <instance_attributes>
>               <attributes>
>                 <nvpair name="ip" value="10.64.110.70"/>
>                 <nvpair name="netmask" value="24"/>
>                 <nvpair name="nic" value="eth0"/>
>               </attributes>
>             </instance_attributes>
>           </primitive>
>         </group>
>       </resources>
>       <constraints>
>          <rsc_location id="rsc_location_IEL" rsc="IEL">
>                  <rule id="prefered_location_IEL" score="100">
>                          <expression attribute="#uname" operation="eq"
> value="node1"/>
>                  </rule>
>          </rsc_location>
>       </constraints>
>     </configuration>
>     <status/>
>   </cib>
>
>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
>



More information about the Linux-HA mailing list