HAProxy track_script + nopreempt not workingKeepalived not honoring nopreemptkeepalived nopreempt option not workingMake keepalived send 0 priority when going to FAULT statekeepalived track_script doesn't seem to runKeepalived unwanted transition to masterkeepalived VRRP_script not failing overHAProxy stats page not workingHAProxy don't balancing requests between nodes of Galera clusterkeepalived failover downtimeWhy doesn't keepalived track_script restart keepalived when HAProxy drops out?
How to test if argument is a single space?
Three knights or knaves, three different hair colors
What defines a person who is circumcised "of the heart"?
What is the required burn to keep a satellite at a Lagrangian point?
Shell builtin `printf` line limit?
Sony VAIO Duo 13 Wifi not working on Ubuntu 16.04
How can I reduce the size of matrix?
Anatomically correct Guivre
VHDL: Why is it hard to desgin a floating point unit in hardware?
Why do testers need root cause analysis?
mmap: effect of other processes writing to a file previously mapped read-only
Is there a word for pant sleeves?
Is it normal to "extract a paper" from a master thesis?
Is being an extrovert a necessary condition to be a manager?
Keeping the dodos out of the field
Managing heat dissipation in a magic wand
Can someone provide me the list of SOQL exceptions?
Meaning of "half-crown enclosure"
Find this Unique UVC Palindrome ( ignoring signs and decimal) from Given Fractional Relationship
Is ideal gas incompressible?
Is there any mention of ghosts who live outside the Hogwarts castle?
How would a physicist explain this starship engine?
Can diplomats be allowed on the flight deck of a commercial European airline?
Is a world with one country feeding everyone possible?
HAProxy track_script + nopreempt not working
Keepalived not honoring nopreemptkeepalived nopreempt option not workingMake keepalived send 0 priority when going to FAULT statekeepalived track_script doesn't seem to runKeepalived unwanted transition to masterkeepalived VRRP_script not failing overHAProxy stats page not workingHAProxy don't balancing requests between nodes of Galera clusterkeepalived failover downtimeWhy doesn't keepalived track_script restart keepalived when HAProxy drops out?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have 2 nodes with Keepalived v1.2.13, in Amazon AWS VPC.
I'm trying to achieve this scenario, assuming Node1 is MASTER:
If I stop HAProxy or stop keepalived or stop the node, failover to Node2.
If I start HAProxy back up on Node1 or start keepalived or start the node, do not failover to Node1 (no flapping).
With the following configuration, only by stopping keepalived or stopping the node, does the failover works. The priority change due to the track_script doesn't seem to affect the MASTER election.
Node1
vrrp_script chk_haproxy # Requires keepalived-1.1.13
script "killall -0 haproxy" # cheaper than pidof
interval 2 # check every 2 seconds
fall 2
weight 2 # add 2 points of prio if OK
vrrp_instance VI_1
advert_int 2
state BACKUP
nopreempt
interface eth0
virtual_router_id 51
priority 101
unicast_peer
172.17.16.10
notify_master "/etc/keepalived/randomscript.sh"
track_script
chk_haproxy
Node2
vrrp_script chk_haproxy # Requires keepalived-1.1.13
script "killall -0 haproxy" # cheaper than pidof
interval 2 # check every 2 seconds
fall 2
weight 2 # add 2 points of prio if OK
vrrp_instance VI_1
advert_int 2
state BACKUP
nopreempt
interface eth0
virtual_router_id 51
priority 100
unicast_peer
172.17.16.11
notify_master "/etc/keepalived/randomscript.sh"
track_script
chk_haproxy
haproxy keepalived
add a comment |
I have 2 nodes with Keepalived v1.2.13, in Amazon AWS VPC.
I'm trying to achieve this scenario, assuming Node1 is MASTER:
If I stop HAProxy or stop keepalived or stop the node, failover to Node2.
If I start HAProxy back up on Node1 or start keepalived or start the node, do not failover to Node1 (no flapping).
With the following configuration, only by stopping keepalived or stopping the node, does the failover works. The priority change due to the track_script doesn't seem to affect the MASTER election.
Node1
vrrp_script chk_haproxy # Requires keepalived-1.1.13
script "killall -0 haproxy" # cheaper than pidof
interval 2 # check every 2 seconds
fall 2
weight 2 # add 2 points of prio if OK
vrrp_instance VI_1
advert_int 2
state BACKUP
nopreempt
interface eth0
virtual_router_id 51
priority 101
unicast_peer
172.17.16.10
notify_master "/etc/keepalived/randomscript.sh"
track_script
chk_haproxy
Node2
vrrp_script chk_haproxy # Requires keepalived-1.1.13
script "killall -0 haproxy" # cheaper than pidof
interval 2 # check every 2 seconds
fall 2
weight 2 # add 2 points of prio if OK
vrrp_instance VI_1
advert_int 2
state BACKUP
nopreempt
interface eth0
virtual_router_id 51
priority 100
unicast_peer
172.17.16.11
notify_master "/etc/keepalived/randomscript.sh"
track_script
chk_haproxy
haproxy keepalived
I also tried on both nodes : state EQUAL, priority 100. This cause a race condition when both instances are booting at the same time, both transition to MASTER, execute the randomscript.sh, and 4-5 seconds after that one node transition to BACKUP, but I don't want the script to be executed.
– Bastien974
Apr 23 '15 at 12:52
migrate your cluster to pacemaker
– c4f4t0r
Jan 8 at 12:34
add a comment |
I have 2 nodes with Keepalived v1.2.13, in Amazon AWS VPC.
I'm trying to achieve this scenario, assuming Node1 is MASTER:
If I stop HAProxy or stop keepalived or stop the node, failover to Node2.
If I start HAProxy back up on Node1 or start keepalived or start the node, do not failover to Node1 (no flapping).
With the following configuration, only by stopping keepalived or stopping the node, does the failover works. The priority change due to the track_script doesn't seem to affect the MASTER election.
Node1
vrrp_script chk_haproxy # Requires keepalived-1.1.13
script "killall -0 haproxy" # cheaper than pidof
interval 2 # check every 2 seconds
fall 2
weight 2 # add 2 points of prio if OK
vrrp_instance VI_1
advert_int 2
state BACKUP
nopreempt
interface eth0
virtual_router_id 51
priority 101
unicast_peer
172.17.16.10
notify_master "/etc/keepalived/randomscript.sh"
track_script
chk_haproxy
Node2
vrrp_script chk_haproxy # Requires keepalived-1.1.13
script "killall -0 haproxy" # cheaper than pidof
interval 2 # check every 2 seconds
fall 2
weight 2 # add 2 points of prio if OK
vrrp_instance VI_1
advert_int 2
state BACKUP
nopreempt
interface eth0
virtual_router_id 51
priority 100
unicast_peer
172.17.16.11
notify_master "/etc/keepalived/randomscript.sh"
track_script
chk_haproxy
haproxy keepalived
I have 2 nodes with Keepalived v1.2.13, in Amazon AWS VPC.
I'm trying to achieve this scenario, assuming Node1 is MASTER:
If I stop HAProxy or stop keepalived or stop the node, failover to Node2.
If I start HAProxy back up on Node1 or start keepalived or start the node, do not failover to Node1 (no flapping).
With the following configuration, only by stopping keepalived or stopping the node, does the failover works. The priority change due to the track_script doesn't seem to affect the MASTER election.
Node1
vrrp_script chk_haproxy # Requires keepalived-1.1.13
script "killall -0 haproxy" # cheaper than pidof
interval 2 # check every 2 seconds
fall 2
weight 2 # add 2 points of prio if OK
vrrp_instance VI_1
advert_int 2
state BACKUP
nopreempt
interface eth0
virtual_router_id 51
priority 101
unicast_peer
172.17.16.10
notify_master "/etc/keepalived/randomscript.sh"
track_script
chk_haproxy
Node2
vrrp_script chk_haproxy # Requires keepalived-1.1.13
script "killall -0 haproxy" # cheaper than pidof
interval 2 # check every 2 seconds
fall 2
weight 2 # add 2 points of prio if OK
vrrp_instance VI_1
advert_int 2
state BACKUP
nopreempt
interface eth0
virtual_router_id 51
priority 100
unicast_peer
172.17.16.11
notify_master "/etc/keepalived/randomscript.sh"
track_script
chk_haproxy
haproxy keepalived
haproxy keepalived
edited Apr 23 '15 at 15:48
Bastien974
asked Apr 22 '15 at 22:49
Bastien974Bastien974
84493153
84493153
I also tried on both nodes : state EQUAL, priority 100. This cause a race condition when both instances are booting at the same time, both transition to MASTER, execute the randomscript.sh, and 4-5 seconds after that one node transition to BACKUP, but I don't want the script to be executed.
– Bastien974
Apr 23 '15 at 12:52
migrate your cluster to pacemaker
– c4f4t0r
Jan 8 at 12:34
add a comment |
I also tried on both nodes : state EQUAL, priority 100. This cause a race condition when both instances are booting at the same time, both transition to MASTER, execute the randomscript.sh, and 4-5 seconds after that one node transition to BACKUP, but I don't want the script to be executed.
– Bastien974
Apr 23 '15 at 12:52
migrate your cluster to pacemaker
– c4f4t0r
Jan 8 at 12:34
I also tried on both nodes : state EQUAL, priority 100. This cause a race condition when both instances are booting at the same time, both transition to MASTER, execute the randomscript.sh, and 4-5 seconds after that one node transition to BACKUP, but I don't want the script to be executed.
– Bastien974
Apr 23 '15 at 12:52
I also tried on both nodes : state EQUAL, priority 100. This cause a race condition when both instances are booting at the same time, both transition to MASTER, execute the randomscript.sh, and 4-5 seconds after that one node transition to BACKUP, but I don't want the script to be executed.
– Bastien974
Apr 23 '15 at 12:52
migrate your cluster to pacemaker
– c4f4t0r
Jan 8 at 12:34
migrate your cluster to pacemaker
– c4f4t0r
Jan 8 at 12:34
add a comment |
1 Answer
1
active
oldest
votes
I ended up using on both nodes :
state EQUAL
priority 100
The race condition was due to some kind of issue with the security group of the instances. So this is an issue specific to AWS.
For an unknown reason, VRRP Unicast works even though not explicitly allowed in the security group. I explicitly opened it (Custom Protocol 112) and it fixed the issue. It seems like it takes time to allow the packet during the initialization of a stack.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f684836%2fhaproxy-track-script-nopreempt-not-working%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I ended up using on both nodes :
state EQUAL
priority 100
The race condition was due to some kind of issue with the security group of the instances. So this is an issue specific to AWS.
For an unknown reason, VRRP Unicast works even though not explicitly allowed in the security group. I explicitly opened it (Custom Protocol 112) and it fixed the issue. It seems like it takes time to allow the packet during the initialization of a stack.
add a comment |
I ended up using on both nodes :
state EQUAL
priority 100
The race condition was due to some kind of issue with the security group of the instances. So this is an issue specific to AWS.
For an unknown reason, VRRP Unicast works even though not explicitly allowed in the security group. I explicitly opened it (Custom Protocol 112) and it fixed the issue. It seems like it takes time to allow the packet during the initialization of a stack.
add a comment |
I ended up using on both nodes :
state EQUAL
priority 100
The race condition was due to some kind of issue with the security group of the instances. So this is an issue specific to AWS.
For an unknown reason, VRRP Unicast works even though not explicitly allowed in the security group. I explicitly opened it (Custom Protocol 112) and it fixed the issue. It seems like it takes time to allow the packet during the initialization of a stack.
I ended up using on both nodes :
state EQUAL
priority 100
The race condition was due to some kind of issue with the security group of the instances. So this is an issue specific to AWS.
For an unknown reason, VRRP Unicast works even though not explicitly allowed in the security group. I explicitly opened it (Custom Protocol 112) and it fixed the issue. It seems like it takes time to allow the packet during the initialization of a stack.
answered Apr 23 '15 at 17:48
Bastien974Bastien974
84493153
84493153
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f684836%2fhaproxy-track-script-nopreempt-not-working%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I also tried on both nodes : state EQUAL, priority 100. This cause a race condition when both instances are booting at the same time, both transition to MASTER, execute the randomscript.sh, and 4-5 seconds after that one node transition to BACKUP, but I don't want the script to be executed.
– Bastien974
Apr 23 '15 at 12:52
migrate your cluster to pacemaker
– c4f4t0r
Jan 8 at 12:34