bhouse-nexthop commented on issue #11710: URL: https://github.com/apache/cloudstack/issues/11710#issuecomment-3496610863
> it looks like r-270-VM had some issues. > > However, keepalived listens on the `eth2` interface so it could not be the root cause. can you search `vrrp` in /var/log in the VRs to see if there were some errors ? > > keepalived highly relates the VRRP configurations on routers. the root cause might be a router configuration. Yes, I gave the reason in the last reply: "The keepalived goes dual primary because the configurations don't match between nodes so it rejects the other node due to this mismatch and both go primary. " But to be more explicit, here are the log entries: ``` Nov 6 11:02:30 r-271-VM Keepalived_vrrp[240595]: Script user 'keepalived_script' does not exist Nov 6 11:02:30 r-271-VM Keepalived_vrrp[240595]: SECURITY VIOLATION - scripts are being executed but script_security not enabled. Nov 6 11:02:30 r-271-VM Keepalived_vrrp[240595]: VRRP_Script(heartbeat) succeeded Nov 6 11:02:30 r-271-VM Keepalived_vrrp[240595]: (inside_network) Entering BACKUP STATE Nov 6 11:02:31 r-271-VM Keepalived_vrrp[240595]: (inside_network) ip address associated with VRID 51 not present in MASTER advert: 10.252.4.1 Nov 6 11:02:32 r-271-VM Keepalived_vrrp[240595]: (inside_network) ip address associated with VRID 51 not present in MASTER advert: 10.252.4.1 Nov 6 11:02:33 r-271-VM Keepalived_vrrp[240595]: (inside_network) ip address associated with VRID 51 not present in MASTER advert: 10.252.4.1 Nov 6 11:02:34 r-271-VM Keepalived_vrrp[240595]: (inside_network) Entering MASTER STATE ``` So essentially it ignores the peer as the config is different and goes master. This obviously brings *everything* down as the VIP gets installed on all interfaces which already exists in the broadcast domain. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
