Put more simply ... I have modified the hbaping HBcomm plugin to simply stat a file on the local filesystem (instead of checking an hba). My hope was when I removed the file, the other node would be declared dead and the resources would fail over.
Needless to say, it didn't work the way I hoped. When I start both nodes with the line myping othernodename in ha.cf, I end up split brain, each node saying the other is "not in our membership list". Theoretically, SHOULD this work? It's certainly possible I fat-fingered something. Or do I need something like a modified ipfail module instead of an HBcomm plugin? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, July 22, 2008 5:38 AM To: [email protected] Subject: Linux-HA Digest, Vol 56, Issue 68 Hi all, We have a need to configure heartbeat to use an additional input as an indication of peer failure. This is a two-node system. We already have a "peer death" indication that we would like to use to tell heartbeat that the peer is definitely dead, so we are safe to assume its resources. We have a serial communication path between the nodes. I started by looking at hbaping and thinking I would build a similar plugin, but from what I've read, a modified ipfail is closer to what I need. Is this the right path? Or should I be looking at something else? Thanks, Mark _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
