RE: Rebooting first machine causes wackamole onsecond machine to abort

that's what it does for me...the former primary doesn't reclaim the ip until you manually fail it back.


-----Original Message-----
From:	David Osborne [mailto:[email protected]]
Sent:	Wed 5/14/2003 9:43 AM
To:	[email protected]
Cc:	
Subject:	Re: [Wackamole-users] Rebooting first machine causes wackamole onsecond machine to abort
Ciprian

Thanks for the quick reply -- that solved the problem. The second
wackamole kept running and took over the virtual IP.

Next problem is, however, after rebooting the first machine (and
starting spread & wackamole on it), it configs eth0:1 with the virtual
IP, even though the second one still has it and I have Prefer None in
the wackamole.conf. With "prefer none", I expected the VIP to stay on
the second machine and that the first machine wouldn't try to claim it
back.

David

On Wed, 2003-05-14 at 15:15, Ciprian Tutu wrote:
> Hi,
> 
> I would recommend setting up Spread not to use multicast. It looks
> like you have a multicast issue on your network.
> Try this first and see if the problem persists:
> 
> Spread_Segment  128.243.40.255:4803 {
>         haydn   128.243.40.92
>         mozart  128.243.40.93
>         mahler  128.243.40.94
> }
> 
> Ciprian

-- 
David Osborne                         [email protected]
Central Systems & Security Team
Information Services
The University of Nottingham    http://www.nottingham.ac.uk/~cczdao/


_______________________________________________
wackamole-users mailing list
[email protected]
http://lists.backhand.org/mailman/listinfo/wackamole-users