On 5/22/07, Tao Yu <[EMAIL PROTECTED]> wrote:
I am using heartbeat 2.0.8.Two scenarios: 1. start heartbeat with no resource defined in cib.xml. Then try to add an empty group by sending message "add_grp group_1" The response message never comes back. In this case, the cib.xml is like the following: <cib> <configuration> <crm_config> <cluster_property_set id="cib-bootstrap-options"> <attributes> <nvpair id="cib-bootstrap-options-default-resource-failure-stickiness" name="default-resource-failure-stickiness" value="INFINITY"/> <nvpair id="cib-bootstrap-options-default-resource-stickiness" name="default-resource-stickiness" value="INFINITY"/> <nvpair id="cib-bootstrap-options-last-lrm-refresh" name="last-lrm-refresh" value="1179778632"/> </attributes> </cluster_property_set> </crm_config> <nodes/> <resources/> <constraints/> </configuration> </cib> 2. Start heartbeat with some resource defined in the group, like an IPaddr, delete the IPaddr resource and then add the IPaddr resource again by sending msg to mgmtd "add_rsc ipaddr_192_168_0_108 ocf IPaddr heartbeat group_1 noclone 0 0 nomaster 0 0 ip_param_1 ip 192.168.0.108" The response message never comes back. Looks in both cases, heartbeat is in some funny state. Is this a bug or there are some ground-rules need to be followed?
logs? _______________________________________________ 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
