On Tue, Feb 25, 2003 at 02:05:41PM +0100, Uwe Kruse wrote:
> "LinuxVirtualServer.org users mailing list."
> <lvs-users@xxxxxxxxxxxxxxxxxxxxxx> schrieb am 25.02.03 13:14:33:
> > On Tue, Feb 25, 2003 at 12:17:11PM +0100, Uwe Kruse wrote:
> > > Wrong Interface for VIP:
> > >
> > > heartbeat: 2003/02/25_12:11:10 info: Removing conflicting loopback lo:0.
> > > heartbeat: 2003/02/25_12:11:10 info: /sbin/ifconfig lo:0 down
> > > heartbeat: 2003/02/25_12:11:10 info: /sbin/route -n del -host 172.20.1.166
> > > heartbeat: 2003/02/25_12:11:10 info: /sbin/ifconfig lo:0 172.20.1.166
> > > netmask 255.255.255.255 broadcast 172.20.1.166
> > >
> > > I think, this should be eth0:0, not lo:0.
> > >
> > > heartbeat: 2003/02/25_12:11:10 ERROR: Could not locate obtain hardware
> > > address for lo
> > > heartbeat: 2003/02/25_12:11:10 warning: Return code 1 from
> > > /etc/ha.d/resource.d/IPaddr
> > Which version of heartbeat are you using? You should get the latest
> > 1.0.1 if you have not done so already.
> Is aktiv.
> > What does your routing table look like? the IPaddr resource for
> > hearbteat tries to work out which real interface to add a virtual
> > interface for the VIP on based on the kernel routing table.
> > If is routed out 172.20.1.166 after the conflicing looback on
> > lo:0 is down, then the interface will be brought up on lo:0
> > instead of eth0:0. I suspect that this is what is happening.
> I put an sleep 10 into the IPaddr after the code for:
> Removing conflicting loopback lo:0,
> but it doesn't help.
> When i look with netstat -rn after the failover, there ist no route to my vip.
That is very curious, I guess there must be a bug in there somewhere.
Can you try stutting down hearbteat and running IPaddr manualy, possibly
with bash -x to track down where the problem is?