Thanks for taking the time to post, I'm hoping you could clarify a bit.
From the linux-ha documentation on the ucast directive:
Note that ucast directives which go to the local machine are effectively
ignored. This allows the ha.cf directives on all machines to be identical.
This would seem to contradict what you are saying about the active
primary needing to see its own heartbeat in order to hold on to its
resources. Adding to this is the fact that if we restart heartbeat on
the primary it comes up as normal and not seeing a heartbeat from the
secondary, assumes control of the resources. If the problem was lack of
a local heartbeat I don't understand why the server could come back up
like this.
--
Regards,
Chris
Chris Huber-Lantz
ScratchSpace Inc.
(831) 621-7928
http://www.scratchspace.com
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
