Solaris 10 snmpd Core Dumps In var_ipAddrEntry Resulting in snmpwalk Timeout (Doc ID 1571239.1)

Last updated on AUGUST 01, 2016

Applies to:

Solaris Operating System - Version 10 3/05 to 10 1/13 U11 [Release 10.0]
Information in this document applies to any platform.

Symptoms

After migrating a Solaris 10 zone to a Solaris 11 host, snmpwalk times out, preventing consistent monitoring:

IP-MIB::ipReasmTimeout.0 = INTEGER: 15
IP-MIB::ipReasmReqds.0 = Counter32: 0
IP-MIB::ipReasmOKs.0 = Counter32: 0
IP-MIB::ipReasmFails.0 = Counter32: 0
IP-MIB::ipFragOKs.0 = Counter32: 0
IP-MIB::ipFragFails.0 = Counter32: 0
IP-MIB::ipFragCreates.0 = Counter32: 0
Timeout: No Response from solarishost

The snmpwalk timeout is due to a core dump of the /usr/sfw/sbin/snmpd process. A pstack on the snmpd core file shows the following stack:

core 'core' of 21131:   /usr/sfw/sbin/snmpd
ffffffff7b600d40 memcpy (4, ffffffff7fff7d64, 60, 2, ffffffff7e3b5da8,
ffffffff7fff7dc4) + 244
ffffffff7e3b5fdc var_ipAddrEntry (ffffffff7fff7ff8, 100471d80, 100471d60, 0,
ffffffff7fff7fd0, ffffffff7fff7fd8) + 1dc
ffffffff7e10e900 netsnmp_old_api_helper (10014d3d0, 100150ae0, 10044cb50,
100440700, 0, 0) + 150
ffffffff7e71d23c netsnmp_call_handler (10014d3d0, 100150ae0, 10044cb50,
100440700, 8, ffffffff7c64e9f0) + 184
ffffffff7e71d3c4 netsnmp_call_next_handler (10014d410, 100150ae0, 10044cb50,
100440700, ffffffff7b700200, 0) + 94
ffffffff7e109eac netsnmp_bulk_to_next_helper (10014d410, 100150ae0,
10044cb50, 100440700, ffffffff7c63e000, 0) + 64
ffffffff7e71d06c netsnmp_call_handlers (100150ae0, 10044cb50, 100440700,
fffffffffffffff8, 0, 10044cb70) + 31c
ffffffff7e710e10 handle_var_requests (10046bc10, 0, 0, 0, 0, 49) + c8
ffffffff7e712924 handle_pdu (10046bc10, 5, 0, 0, 0, 0) + 2dc
ffffffff7e7123d0 netsnmp_handle_request (10046bc10, 0, 10043fca0, 10046bc10,
0, 10046bc10) + 228
ffffffff7e70f7a0 handle_snmp_packet (1, 10043fe10, 1530c920, 10043fca0, 0,
10043fca0) + 298
ffffffff7de79b18 _sess_process_packet (10044c400, 10043fe10, 10045af70,
10043fc10, 100459ea0, 10) + a30
ffffffff7de7b1e8 _sess_read (10044c400, ffffffff7fffd4f8, 10, 10, 10000, 0) +
1490
ffffffff7de7b254 snmp_sess_read (10044c400, ffffffff7fffd4f8,
ffffffff7c6468c8, ffffffff7fff94f8, 0, 0) + 24
ffffffff7de79d1c snmp_read (ffffffff7fffd4f8, ffffffff7fffd4f8,
ffffffff7fffb4f8, ffffffff7fff94f8, ffffffff7fff94e8, 10044c400) + 3c
0000000100004a60 receive (0, 4, ffffffff7dedc788, 0, 0, 0) + 7c0
00000001000040b8 main (1, ffffffff7ffffb78, ffffffff7ffffb88,
ffffffff7c44bfc0, ffffffff7ea00200, ffffffff7b700200) + 1708
000000010000253c _start (1, ffffffff7ffffb78, ffffffff7ffffb88, 0, 103d58,
ffffffff7f536268) + 17c

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms