Hello list, I have two nodes (rnd-dev1, rnd-dev2) running RH4 with CentOS based rpm install of heartbeat 2.0.7
I'm seeing a problem where heartbeat prefers to always run resources on node2, even when I deliberately make them return 1 on monitor action. The only scenario where heartbeat chooses to run them on node1 is when I stop heartbeat on node2, if I start heartbeat again on node2 the resources will migrate there again (and continue failing). Have I configured something wrong in the cib? (attached below) Thank you for you help, Maxim. ======== CIB.XML ======== <cib> <configuration> <crm_config> <cluster_property_set id="cib-bootstrap-options"> <attributes> <nvpair id="cib-bootstrap-options-last-lrm-refresh" name="last-lrm-refresh" value="1184246165"/> </attributes> </cluster_property_set> </crm_config> <nodes> <node id="9340c47f-fb6d-4261-8e40-0a76af433285" uname="rnd-dev2" type="normal"/> <node id="a2f38ac4-ec05-4c89-84a9-7116a8e84e48" uname="rnd-dev1" type="normal"/> </nodes> <resources> <group id="grp_1"> <primitive id="rsc_ip" class="ocf" type="IPaddr" provider="heartbeat"> <instance_attributes id="ia_ip"> <attributes> <nvpair id="nvpair_ip_address" name="ip" value="192.168.31.86"/> </attributes> </instance_attributes> </primitive> <primitive id="rsc_dcn" class="ocf" type="dcn_agent" provider="ML"> <operations> <op id="op_dcn_monitor" name="monitor" timeout="3s" interval="1s"/> </operations> </primitive> <primitive id="rsc_mng" class="ocf" type="mng_agent" provider="ML"> <operations> <op id="op_mng_monitor" name="monitor" timeout="3s" interval="3s"/> </operations> </primitive> </group> </resources> <constraints/> </configuration> </cib> ======== CIB.XML ======== -- Cheers, Maxim Veksler "Free as in Freedom" - Do u GNU ? _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems