Keepalived keeps forcing new elections

[Brad Chang]

Hi Alexandre

fw2 has always used 255 as priority.  I will upgrade fw2 to 1.1.7 and try that 
for a while... but it has been running for weeks without issues..

thanks alot for your input
-Brad


Quoting Alexandre Cassen <Alexandre.Cassen at wanadoo.fr>:

> Hi Brad,
> 
> >fw1 is set as backup and priority of 250
> >keepalived version 1.1.7 kernel 2.4.20
> >fw2 is set as master and priority of 255
> >keepalived 1.1.6 patched kernel 2.4.25
> >
> >the keepalived boxes do roughly 14Mb/s please let me know if anyone wants
> any
> >more information about these servers.  I am not sure why they started to 
> >do this
> >but restarting keepalived on both boxes did nothing.  I had to shutdown 
> >fw1 box
> >and restart keepalived on fw2 to get it to work properly again.  as soon as
> I
> >did this and confirmed everything was still working I plugged back in fw1
> and
> >both seem to be working fine now.
> 
> ?... hmm wired here... in a first step I will answer like constructor 
> customer care : "heu... use the same release of keepalived on your both 
> node" :) a a aa :)
> 
> seriously, hmm... never use 255 as priority since this is an VRRP internal 
> value. use value between 1..254. on the receiving point, 255 is synonymous 
> of force master transition which is a special state into the VRRP FSM. 
> Never tested but in a first thought this might be an issue.
> 
> best regards,
> Alexandre 
> 
> 
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users at LinuxVirtualServer.org
> Send requests to lvs-users-request at LinuxVirtualServer.org
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
> 






Thanks
-Brad Chang
-http://www.dotnoc.com


----------------------------------------------------------------
http://www.dotnoc.com hosting the way it should be.