> Can you try using the latest ucarp (1.4, plus some patches)? The
> behavior in situations like this was a little unpredictable before.
>
> Download ucarp 1.4. Please note the unofficial 1.4 release is broken
> and will not work without patching.
>
http://download.pureftpd.org/pub/ucarp/ucarp-1.4.tar.gz
>
> Apply this patch for multicast (credit Petya Kohts):
>
http://imperium.lenin.ru/~nit/ucarp/ucarp-1.4-yandex-multicast.patch
>
> Apply the attached patch (ucarp-1.4patched-nonpreferredfix.patch,
> credit Greg Walton) to improve master election.
>
> Steve
>
>
>
>
>
> On Sat, May 3, 2008 at 12:02 PM, <okahei@gmail.com> wrote:
> > Hi all
> >
> > I have this conf :
> >
> > Node1:
> >
> > ucarp -i eth1 -s 176.12.0.2 -v 10 -z -b 1 -k 0 --neutral -B -p
> > ucarpov -a 192.168.3.4 --upscript=/etc/ucarp/vip-up.sh
> > --downscript=/etc/ucarp/vip-down.sh
> >
> > Node2:
> >
> > ucarp -i eth1 -s 176.12.0.1 -v 10 -z -b 1 -k 0 --neutral -B -p
> > ucarpov -a 192.168.3.4 --upscript=/etc/ucarp/vip-up.sh
> > --downscript=/etc/ucarp/vip-down.sh
> >
> > With Node2 as a Master if i shutdown it Node1 becomes the Master. All rigth
> >
> > But when i turn on Node2, it gets the Masters role and Node1 become Backup.
> >
> > In my config i dont have a prefered master (i don't want this
> > behaviour) but Node2 get allways the Master Role if i reboot it.
> >
> > This not happend if i reboot Node1.
> >
> > thanks.
> >
>