Dear Member of the list,

I'm running ( or trying to) heartbeat 2 on 3 debian stable amd64 boxes.
heartbeat's version 2.0.7-2.
My goal is to have a cluster of 3 boxes running:
heartbeat on top of
ldirectord on top of
ipvsadm on top of
lighttpd.
Should be a fairly common construct.
I used as guide for this set up an article published in linux magazine
fr.(N°97)
My 3 boxes are f1_3,f2_3,f3_3.
On each I set before starting heartbeat:
-the lo interface to the virtual IP
-the necessary kernel parameters (arp_ignore, arp_announce)
of my ipvs cluster.
The script I use for this can be found on:
http://www.maje.biz/downloads/lvsdr
The ressources configured in my haresources are:
f1_3 IPaddr2::here_my_virtual_ip/27/eth1/here_the_bcast_ip_of subnet
ldirectord

If I understand the way it works, the master in this case f1_3 will run
the resource IPaddr2 and take following actions:
-remove VIP from lo
-store it in /var/run/heartbeat/rsctmp/IPaddr/my_virtual_ip
-set the eth1 to my my_virtual_ip
-start ldirectord

The problem is that IPaddr2 never makes the switch lo->eth1 nor stores
anything in var/run/heartbeat/rsctmp/IPaddr/my_virtual_ip.
but exits with a succes msg in ha.log
Some searching in the archives pinpointed on a similar problem with IPaddr.
I can't tell for the time being if IPaddr and IPaddr2 do use same
framework functions so I don't know if those problems are related.

in /usr/lib/ocf/resource.d/heartbeat/IPaddr2
there is a function remove_conflicting_loopback() that I think should be
called during this process, but is never called.

Did somebody experience the same problem or am I alone doing something
very stupid?
I'll try digging deeper into this, help, hints are most welcome.
Is some more info mandatory to get a better picture I'll be happy to
provide.

I switch my headlight back on and put my hands back in the grease.

regards

Cedric





_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to