SNMP MADMAN mib Slow to Repond and snmpd Core Dumps
(Doc ID 1393015.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle Communications Messaging Server - Version 6.3 and later
Information in this document applies to any platform.
SNMP requests for the MADMAN mib, which are handled by the madmand subagent process, are slow and/or the madmand process exits, which causes the SNMP master agent to dump core.
Also, messages like these in the /var/adm/messages file:
Jan 10 09:45:15 mta02 last message repeated 5 times
Jan 10 09:45:55 mta02 net-snmp: [ID 702911 daemon.warning] AgentX master agent failed to respond to ping. Attempting to re-register.
Jan 10 09:50:49 mta02 last message repeated 4 times
Jan 10 09:52:20 mta02 net-snmp: [ID 702911 daemon.warning] AgentX master agent failed to respond to ping. Attempting to re-register.
Jan 10 09:53:13 mta02 last message repeated 1 time
Note that although the process name in the messages above is "net-snmp", the process id is that of the madmand process, so the above messages are coming from madmand.
See SNMP Support for details of how to configure SNMP support for Messaging Server - https://docs.oracle.com/cd/E63708_01/doc.801/e63711/msadm_snmp.htm#MSVAG889
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document