Snmpd running out of resources allocated and need a bigger resource pool and/or there's a leak
Unsigned allocations have 236595 instances taking 0xd11588(13,702,536) bytes.
Unsigned allocations of size 0x58 have 111625 instances taking 0x95e318(9,823,000) bytes.
Unsigned allocations of size 0x18 have 99450 instances taking 0x246b70(2,386,800) bytes.
Unsigned allocations of size 0x28 have 18801 instances taking 0xb79a8(752,040) bytes.
Unsigned allocations of size 0x68 have 6645 instances taking 0xa8b88(691,080) bytes.
Unsigned allocations of size 0x258 have 70 instances taking 0xa410(42,000) bytes.
Unsigned allocations of size 0x268 have 2 instances taking 0x4d0(1,232) bytes.
Unsigned allocations of size 0x688 have 1 instances taking 0x688(1,672) bytes.
Unsigned allocations of size 0x1268 have 1 instances taking 0x1268(4,712) bytes.
236595 allocations use 0xd11588 (13,702,536) bytes.
The memory stat can be captured by the following command . Below are two examples from LAB with normal SNMP and other from customer in problematic set up.
#memstats -r group-stats -f -u mb -s name:parGid:min:max:consumed:rminpeak -u mb > /tmp/snmp.txt
#cat /tmp/snmp.txt | grep -E "consumed|snmp"
Selected columns : gid:name:parGid:min:max:rMinPeak:consumed gid name parGid min max rMinPeak consumed
796 snmpd 15 0 0 0 0 > this is normal usage >> from LAB
#cat /tmp/snmp.txt | grep -E "consumed|snmp"
Selected columns : gid:name:parGid:min:max:rMinPeak:consumed gid name parGid
805 snmpd 15 22 22 23 21 >> this is exhaustive usage of memory by snmpd >> from customer environment (with issue )