What is the correct way to disable preempt for keepalived about keepalived HOT 4 CLOSED

The correct way to disable preempt is to specify nopreempt in the VRRP instance.

If you need any further assistance, you will need to post the keepalived configurations for each of your three systems, and the full keepalived system logs from each of the three systems from the time that keepalived started on those systems. We can then reopen this issue.

I have tested your configuration and nopreempt works for me as expected.

from keepalived.

The correct way to disable preempt is to specify nopreempt in the VRRP instance.

If you need any further assistance, you will need to post the keepalived configurations for each of your three systems, and the full keepalived system logs from each of the three systems from the time that keepalived started on those systems. We can then reopen this issue.

I have tested your configuration and nopreempt works for me as expected.

@pqarmitage For "nopreempt" in the posted config above, VIP switches over as expected when the node (with VIP) is completely down. However, the VIP did not switch over when node (with VIP) is alive but the track_script keeps failing. Is this expected behavior?

from keepalived.

The track script has a weight of 50, so when the script fails it subtracts 50 from the vrrp priority. To make a vrrp instance go to fault state on failure, weight must not be specified.

from keepalived.

The track script has a weight of 50, so when the script fails it subtracts 50 from the vrrp priority. To make a vrrp instance go to fault state on failure, weight must not be specified.

This is exactly what we are looking for. Thanks a lot @pqarmitage

from keepalived.