Hello all! I am running Heartbeat 2.1.2 on CentOS 4.5 and while testing a two-node cluster I did some shutdowns of a MySQL resource to see how external clients react on the db connection loss and if they reconnect on the successful restart of MySQL by Heartbeat.
I noticed the following behaviour and wonder if this is correct: * shutdown/kill of a ressource without the help of heartbeat * resource monitoring of heartbeat detects the error * stop/start of the resource is initiated and successful * resource is up again but now I kill the resource again before the first monitoring event after start occours * on the first monitoring event heartbeat detects the resource is not running but does not restart the resource again * crm_resrource -P resolves this state and stops/starts the resource Is there a special reason for this behaviour? Regards, Andreas
cib.xml.gz
Description: GNU Zip compressed data
ha-log.gz
Description: GNU Zip compressed data
ha-log_DC.gz
Description: GNU Zip compressed data
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
