Keepalived_vrrp: Warning: Failed to connect to the agentx master agent


#1

Hi community!

I’ve a question about vrrp running on two routers (vyos).

on both nodes i’ve seen (many) repeted log messages like this:

The vrrp configuration looks like this:

vyos1 : vrrp { vrrp-group 1 { advertise-interval 5 hello-source-address 10.200.200.10 preempt true priority 180 run-transition-scripts { master /config/scripts/failover_ip.script } sync-group SYNC_GROUP1 virtual-address 10.200.200.1 } }

vyos2 : vrrp { vrrp-group 1 { advertise-interval 5 hello-source-address 10.200.200.20 preempt true priority 40 run-transition-scripts { master /config/scripts/failover_ip.script } sync-group SYNC_GROUP1 virtual-address 10.200.200.1 } }
any ideas? its a permission problem on failover_ip.script ?

This script its executed correctly…

Thanks in advance!


#2

Hi everyone!

Searching more about this issue i have found that it’s a bug in keepalived code already solved at version keepalived-1.2.17 https://github.com/acassen/keepalived/commit/0250c2cd801d177a89d5ba659a1792a523488caa

The running version of keepalived in vyos is 1.2.2 https://github.com/vyos/vyatta-keepalived/blob/lithium/VERSION

[code]* vrrp: Fix the keepalived mib and agentx warnings. During Keepalived

  • startup, about twenty "duplicate registration" and a couple of "Failed
    
  • to connect to the agentx master agent" warning messages were issued.
    
  • Pairs of the "Failed to connect" warning messages were logged every two
    
  • minutes. The "duplicate registration" warnings happened because VRRP
    
  • called snmp_agent_init twice, once for the keepalived-vrrp MIB, and once
    
  • for the rfc2787-vrrp MIB, however each call to snmp_agent_init also
    
  • tried to register the keepalived-global MIB (which holds data like
    
  • Keepalived version number, SMTP server details, and a "from" email
    
  • address).  It was the second attempt to register this keepalived-global
    
  • MIB that generated the "duplicate registration" warning. The registration
    
  • of the keepalived-global MIB is now only done once under the control of
    
  • a static variable.   init_agent is also called just once under the control
    
  • of the same static variable to prevent it logging a warning message. The
    
  • "Failed to connect" warnings occur because Keepalived does not know how
    
  • to connect to the SNMP AgentX master server.  By default the Agent X
    
  • master server is listening for MIB registrations on a local TCP socket
    
  • with a port number of 705.[/code]

#3

Hello,
this will be likely addressed in 1.2.x


#4

Ok!

Thanks… i will ignore the logs :slight_smile: