How to see keepalived priority number when it changed

keepalived

I have used keepalived to archive high availability for nginx. I set initial priority 101 for MASTER, 100 for BACKUP and I can see /var/log/messages :

Keepalived_vrrp[34483]: VRRP_Script(chk_nginx) failed
Keepalived_vrrp[34483]: VRRP_Instance(VI_1) Received higher prio advert
Keepalived_vrrp[34483]: VRRP_Instance(VI_1) Entering BACKUP STATE
Keepalived_vrrp[34483]: VRRP_Instance(VI_1) removing protocol VIPs

Is there any way to see the changed priority number to look into why my machine change role state?

vrrp_script chk_nginx {
   script "killall -0 nginx"
   interval 1
   weight -2
   fall 2
   rise 1
}

Best Answer

You can use tcpdump to see the advertisements on the wire. This will show you the source machine sending the advertisement that's higher.

tcpdump -vvv -n -i eth0 host 224.0.0.18

Related Solutions

How to configuration keepalived on Amazon EC2

If you're not intimately familiar with keepalived/haproxy, why not just use the AWS ELB?

As for running haproxy on your own (if you're deadset on doing that), I presume you're trying to bounce connections from XMPP server to Casandra 1-4. Why not just install haproxy on the XMPP box? You can configure haproxy like you normally would and then simply point XMPP at 127.0.0.1 - Then you've got 5 boxes in your setup instead of 7.

Why doesn’t keepalived track_script restart keepalived when HAProxy drops out

I'm using a custom track_script now which fixes this. It restarts keepalived if haproxy isn't running. Seems that keepalived only enters BACKUP mode using the default track script on startup/restart, not while it's running ¯\_(ツ)_/¯

#!/bin/sh
# restart keepalive if haproxy died
pid=`/bin/pidof haproxy`
test -z "$pid" && { service keepalived restart &>/dev/null; exit 1; }
exit 0

Best Answer

Related Solutions

How to configuration keepalived on Amazon EC2

Why doesn’t keepalived track_script restart keepalived when HAProxy drops out

Related Topic