[Linux-HA] Is this heartbeat behaviour correct ?
alanr at unix.sh
Fri Aug 5 08:17:53 MDT 2005
Boris Berger wrote:
> Hello all,
> I have tested a 2 node active/passive Heartbeat cluster.
> To check the connection of each node in the external network,
> ipfail is active with a ping towards a third machine, as
> specified in ha.cf file :
> respawn hacluster /usr/lib/heartbeat/ipfail
> ping theThirdMachine
> Before performing the tests, we have the initial situation :
> - Heartbeat is running on both nodes,
> - one service (apache) is running on node 1,
> - no service is running on node 2,
> as specified the haresource file :
> node1 addrIpServ1 apache
> Now I cut simultaneously :
> - the direct connection between the 2 nodes
> - the connection between node 1 and the third machine
> - the connection between node 2 and the third machine
> Then, one can notice in the log that :
> - Apache does not stop on node 1
> - Apache start on node 2.
> So Apache is now running on both nodes.
> Now, if I reestablish :
> - EITHER the connection between node 1 and the third machine ONLY
> - OR the connection between node 2 and the third machine ONLY
> then nothing special is happening, so Apache is still running on both nodes.
> Do you know is this is a normal behaviour ? And how can this be explained ?
It can most probably be explained as a multiple failure you haven't
configured heartbeat to deal with. In other words, a configuration error.
When you restore the direct connection (the only one you are
heartbeating over, I strongly suspect), it will restart heartbeat on
If you want that to work, you need to tell heartbeat to send heartbeats
over all (both?) interfaces - not just the direct connection.
Alan Robertson <alanr at unix.sh>
"Openness is the foundation and preservative of friendship... Let me
claim from you at all times your undisguised opinions." - William
More information about the Linux-HA