[Linux-HA] Heartbeat kills my lo:0, and therefore my LVS-DR

[Nic Pottier]

Sorry, forgot to include some other relevant info.

The heartbeat log as it kills my poor lo:0
Dec  8 18:29:24 n02-bot ResourceManager[30021]: info: Running 
/etc/ha.d/resource.d/IPaddr 192.168.0.120/24/eth0 stop
Dec  8 18:29:24 n02-bot IPaddr[30286]: INFO: /sbin/route -n del -host 
192.168.0.120
Dec  8 18:29:24 n02-bot IPaddr[30286]: INFO: /sbin/ifconfig lo:0 
192.168.0.120 down
Dec  8 18:29:24 n02-bot IPaddr[30286]: INFO: IP Address 192.168.0.120 
released
Dec  8 18:29:24 n02-bot IPaddr[30204]: INFO: IPaddr Success
Dec  8 18:29:24 n02-bot heartbeat: [30011]: info: foreign HA resource 
release completed (standby).

And my haresources:
n01-bot.trileet.com 192.168.0.120/24/eth0 arp-answer 
ldirectord::/etc/ha.d/ldirectord.cf

Note that 'arp-answer' is a resource I wrote to turn on/off arp requests 
for the VIP as RHEL must use arptables to ignore arp requests on lo.

Thanks again,

-Nic

Nic Pottier wrote:
> 
> I'm been trying to set up a two node LVS-DR setup on CentOS 4.4 such as 
> the one outlined here:
> <http://koto.ultramonkey.org/3/topologies/sl-ha-lb-eg.html>
> 
> I feel I have my head wrapped around things rather well after a day of 
> mucking with this and a considerable amount of reading, but I have one 
> last gotcha which despite many workarounds I can't get through.
> 
> On my secondary node (heartbeat controlling ldirectord), heartbeat 
> insists on killing my loopback with the VIP.  This of course prevents 
> that box from accepting any traffic on the VIP, making it unable to 
> answer requests.  Worse still, the primary (live) director believes it 
> to be up since the RIP happily answers.
> 
> This must be something dumb on my part, but I swear I've followed every 
> howto, searched every archive and read every book I could find and I'm 
> not having any luck.
> 
> If I manually bring up lo:0 AFTER heartbeat kills it, sure enough things 
> work fine.
> 
> I even tried writing my own resource to bring lo:0 up when Heartbeat 
> releases it, but the killing takes place AFTER the stop so it doesn't do 
> any good.
> 
> What's the two line answer to this?  I know there must be one, but for 
> the life of me I can't figure it out.
> 
> I'm using the CentOS 4.4 extras packages, namely:
>    heartbeat.x86_64              2.0.7-1.c4     installed
>    heartbeat-ldirectord.x86_64   2.0.7-1.c4     installed
> 
> I promise I'll write a CentOS howto on this when i figure it out.
> 
> Many thanks,
> 
> -Nic