LIBJSNMP_NS_LOG_WARNING - Config Router

The

LIBJSNMP_NS_LOG_WARNING

message reports an internal SNMP warning message.

SYMPTOMS:

When a LIBJSNMP_NS_LOG_WARNING event occurs, a message similar to the following is reported:

bfdd[2226]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Connection refused)
lacpd[1058]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Out of memory (malloc failure)
mib2d[90239]: LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Cannot allocate memory)
idpd[1417]: %DAEMON-4-LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX session to master agent attempted to be re-opened.
lacpd[1106]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register.
pfed: %USER-4-LIBJSNMP_NS_LOG_WARNING: WARNING: Warning: Failed to connect to the agentx master agent (/var/run/snmpd_agentx): Unknown host (/var/run/snmpd_agentx) (Connection refused)

You can see these messages even on perfectly fine systems when the system boots, during restart of the snmpd process, or when a GRES event occurs. These messages will appear when snmpd is busy receiving lots of registration requests from multiple subagents. If the subagent fails to connect/register, it retries and eventually connects to snmpd.

Examine the following output to help determine the cause of this message:

show log messages
show log chassisd
show log jsrpd
show chassis hardware detail

Look for any related events that occurred at or just before the LIBJSNMP_NS_LOG_WARNING message in the syslog output.

Perform these steps:

Follow the instructions under ‘Confirm Causes’.
If this is happening at system boot-up, snmpd restart time, or GRES, these messages are expected and can be ignored.
In rare occurrences the PFED daemon may log the following message after issuing the command “show pfe route ip” on a scaled setup:
```
pfed: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX session to master agent attempted to be re-opened
```
Restarting the PFED daemon will recover the problem. This should be done during a maintenance window, as it will affect transit traffic.
During a maintenance window, as it will impact transit traffic, try restarting the process deamon referenced in the syslog message.
If the log messages continue, open a case with your technical support representative to investigate the issue further.

Related