Re: VRRP entering master state on both nodes in pair

* "Todd D. Taft" <[email protected]>

> Something isn't working as I would expect with my configuration, because 
> shortly after starting keepalived on either system, that system thinks 
> it's the master for both services (even when the other system is up).  
> As such, all requests for both services go to whichever system sent out 
> the arp packets most recently.

Hi Todd,

Check if they two hosts are seeing each others' VRRP advertisements,
for example with with "tcpdump -vni eth0 vrrp". If they don't, check if
your switch has multicast snooping enabled and if so try to disable it.

Do eth0 on both hosts have an IPv4 address/prefix configured that
encompasses 10.1.42.240 and .241? If not, try disabling uRPF with
"sysctl -w net/ipv4/conf/eth0/rp_filter=0".

Why do the instances in state MASTER have a lower priority than the
corresponding instance on the other node with state BACKUP? That seems
backwards to me. For what it's worth, I prefer to let all instances
start out with state BACKUP (they'll elect a master soon enough).

What is the purpose of your track_scripts? They seem to me to only ping
the local host, which should always succeed as long as the host is up,
right?

Tore

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF