Hello all, I have a Heartbeat 2.1.2 two-node cluster installation using three ping nodes to check network connectivity. Today one of the ping nodes was restarted and the loss of one ping node was detected by both nodes at the same time (according to the logs).
The problem was that the pingd score_attribute was only decreased for one node (holding two resource groups) in a first attempt and heartbeat began to stop resources to migrate the groups away. During the resource shutdown the pingd score_attribute of the second node was also decreased and the resource migration was stopped and restarted on the current node. Some seconds later the third ping node was up again, the pingd score_attribute was updated for both nodes and the resources were untouched. My question is: Is there a way to 'tune' the configuration to avoid souch resource restarts and why was the pingd score_attribute updated 'simultaneously' when the ping node came up again but not when it got down? Regards, Andreas
ha.cf.bz2
Description: BZip2 compressed data
ha-log.smsdb05.bz2
Description: BZip2 compressed data
ha-log.smsdb06.DC.bz2
Description: BZip2 compressed data
pe-input-19.bz2
Description: BZip2 compressed data
pe-input-20.bz2
Description: BZip2 compressed data
pe-input-21.bz2
Description: BZip2 compressed data
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
