On Tue, Aug 09, 2011 at 04:03:40PM -0700, Chris Huber-Lantz wrote: > 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.
You would need to send some logs, from "everything ok", just before you shut down one node, to when the remaining node shuts down its resources. This seems to be an "haresources" style cluster? Is haresources identical on both nodes? It has to be. I assume ha.cf is reciprocal with regard to the peer address used on the udp line? I would recommend to just put both IPs as udp lines in the ha.cf, so you can have ha.cf identical on both nodes as well. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
