[Keepalived-devel] nopreempt and FAULT state - keepalived 1.2.7

[Stefan Kärst]

Hi,

I'm using CentOS 6.4 and keepalived 1.2.7 (02/21,2013). I ran a lot of tests to see "nopreempt" working.

According to man page "nopreempt" only works if state is BACKUP. why is this the case?
If network link goes down the state changes to FAULT. If network links comes back keepalived becomes MASTER if it has
highest priority! this makes nopreempt kind of useless.

According to man page "state" doesn't matter a lot because of vrrp election. But, as I tested this with kvm guests it
DOES MATTER a lot. It effectivly starts keepalived e.g. in state MASTER which overrules "nopreempt".
Starting keepalived without "state" option in config file makes "nopreempt" working as excpected -> starting up in state
BACKUP, listen to vrrp and stay BACKUP because of "nopreempt".

As I could not figure out how to search in the list-archives I try this way. (why is a mailman list hosted at sf.net?? -
mailman has such a ... useful webinterface)
Where do I post bugs? sf.net project page seems out of date (files, bugs). I found a new bug which I want to post...


Thanks for reading.
Any answer would be much appreciated.

Regards
Stefan K.

[Paul Robert Marino]

[Strahinja Kustudic]

Hi Stefan,

I had the same problem and it took me a while to figure out how to make
nopreempt work as it should. I finally found the solution by setting both
to BACKUP and setting one server with a priority lower by 1.

Regarding bugs, you can report them on GitHub
https://github.com/acassen/keepalived


Regards,
Strahinja

Post by Stefan Kärst
Hi,
I'm using CentOS 6.4 and keepalived 1.2.7 (02/21,2013). I ran a lot of
tests to see "nopreempt" working.
According to man page "nopreempt" only works if state is BACKUP. why is this the case?
If network link goes down the state changes to FAULT. If network links
comes back keepalived becomes MASTER if it has
highest priority! this makes nopreempt kind of useless.
According to man page "state" doesn't matter a lot because of vrrp
election. But, as I tested this with kvm guests it
DOES MATTER a lot. It effectivly starts keepalived e.g. in state MASTER
which overrules "nopreempt".
Starting keepalived without "state" option in config file makes
"nopreempt" working as excpected -> starting up in state
BACKUP, listen to vrrp and stay BACKUP because of "nopreempt".
As I could not figure out how to search in the list-archives I try this
way. (why is a mailman list hosted at sf.net?? -
mailman has such a ... useful webinterface)
Where do I post bugs? sf.net project page seems out of date (files,
bugs). I found a new bug which I want to post...
Thanks for reading.
Any answer would be much appreciated.
Regards
Stefan K.
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Keepalived-devel mailing list
https://lists.sourceforge.net/lists/listinfo/keepalived-devel