Hi, I have a 2 nodes cluster with eth1 as heartbeat connection between the nodes and eth0 interfaces connected to my clients. I installed ping to test my network connection. I also declared auto_failback=yes in ha.cf, so that when my node comes up after a failure, it get its resources back (it is working, I tested it)
In ha.cf it is configured so respawn root /usr/lib64/heartbeat/pingd -m 100 -d 5s ping_group ping_nodes 10.0.0.210 10.0.0.211 (where 10.0.0.210 and 10.0.0.211 are my nodes.. not sure this is the good way to use pingd but it works, I'd better define other servers, no?) When a network failure occurs over eth0 on node1, all services on node1 are stopped on node1 and restarted on node2, ok. But then when the network failure is repared and node1 comes again in the network, resources don't failback, why not? As the node came in the cluster again and everything is fine. But when restarting the node, everything is ok... Does it mean I need STONITH for such failures? I also get the same behaviour when eth1 fails, the heartbeat signal connection (yes I know there is no redundancy, but these are tests :) ). So my question is, are these behaviour normal? thanks in advance. -- Sébastien Lorandel _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
