We are running a DXi V1000 (2.3.2 55464-Build12).

Quite often (that is: every 3 to 5 minutes) the process "/usr/local/sbin/qtm_snmp_subagent" crashes.

*** glibc detected *** /usr/local/sbin/qtm_snmp_subagent: malloc(): memory corruption: 0x0000000005ff9cc0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x2b4e0c7c5fbe]
/lib64/libc.so.6(__libc_malloc+0x6e)[0x2b4e0c7c7dfe]
/usr/local/gcc-433/lib64/libstdc++.so.6(_Znwm+0x1d)[0x2b4e0be56a6d]
/usr/local/gcc-433/lib64/libstdc++.so.6(_ZNSs4_Rep9_S_createEmmRKSaIcE+0x21)[0x2b4e0be34381]
/usr/local/gcc-433/lib64/libstdc++.so.6(_ZNSs4_Rep8_M_cloneERKSaIcEm+0x2b)[0x2b4e0be34c2b]
/usr/local/gcc-433/lib64/libstdc++.so.6(_ZNSs7reserveEm+0x41)[0x2b4e0be358b1]
/usr/local/gcc-433/lib64/libstdc++.so.6(_ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEE8overflowEi+0xba)[0x2b4e0be2f74a]
/usr/local/gcc-433/lib64/libstdc++.so.6(_ZNSt15basic_streambufIcSt11char_traitsIcEE6xsputnEPKcl+0x38)[0x2b4e0be33a68]
/usr/local/lib/liblog4cplus-1.0.so.4(_ZSt16__ostream_insertIcSt11char_traitsIcEERSt13basic_ostreamIT_T0_ES6_PKS3_l+0x1b5)[0x2b4e09a08945]
/usr/local/sbin/qtm_snmp_subagent(_ZN17TLEMgrAdapterData7AddPairEPKcS1_b+0x154)[0x415d7a]
/usr/local/sbin/qtm_snmp_subagent(getProdID+0x49)[0x40f34a]
/usr/local/sbin/qtm_snmp_subagent(_Z15var_quantumsnmpP8variablePmS1_iS1_PPFiiPhhmS2_S1_mE+0x29c)[0x40cfac]
/usr/local/lib/libnetsnmpagent.so.30(netsnmp_old_api_helper+0x194)[0x2b4e0ac4f114]
/usr/local/lib/libnetsnmpagent.so.30(netsnmp_call_handlers+0x2f7)[0x2b4e0ac5fe37]
/usr/local/lib/libnetsnmpagent.so.30(handle_var_requests+0x8f)[0x2b4e0ac6979f]
/usr/local/lib/libnetsnmpagent.so.30(handle_pdu+0x191)[0x2b4e0ac6b291]
/usr/local/lib/libnetsnmpagent.so.30(netsnmp_handle_request+0xe8)[0x2b4e0ac6d328]
/usr/local/lib/libnetsnmpagent.so.30(handle_snmp_packet+0x1c7)[0x2b4e0ac6d787]
/usr/local/lib/libnetsnmp.so.30[0x2b4e0b4d52ee]
/usr/local/lib/libnetsnmp.so.30(_sess_read+0x6b5)[0x2b4e0b4d6965]
/usr/local/lib/libnetsnmp.so.30(snmp_sess_read2+0x9)[0x2b4e0b4d7259]
/usr/local/lib/libnetsnmp.so.30(snmp_read2+0x23)[0x2b4e0b4d7313]
/usr/local/lib/libnetsnmp.so.30(snmp_read+0x34)[0x2b4e0b4d7364]
/usr/local/lib/libnetsnmpagent.so.30(agent_check_and_process+0xb8)[0x2b4e0ac6dd98]
/usr/local/sbin/qtm_snmp_subagent(main+0xca)[0x40dfea]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x2b4e0c7719f4]
/usr/local/sbin/qtm_snmp_subagent(__gxx_personality_v0+0x179)[0x40bc39]
======= Memory map: ========
00400000-0041e000 r-xp 00000000 08:05 16708537 /usr/local/sbin/qtm_snmp_subagent
0061e000-0061f000 rw-p 0001e000 08:05 16708537 /usr/local/sbin/qtm_snmp_subagent
0061f000-00628000 rw-p 0061f000 00:00 0
05e6c000-06019000 rw-p 05e6c000 00:00 0 [heap]
2b4e08600000-2b4e0861c000 r-xp 00000000 08:05 13389306 /lib64/ld-2.5.so
2b4e0861c000-2b4e0861d000 rw-p 2b4e0861c000 00:00 0
2b4e0861d000-2b4e0861e000 rw-s 00000000 00:09 98307 /SYSV7905bc9d (deleted)
2b4e0862a000-2b4e0862b000 rw-p 2b4e0862a000 00:00 0
2b4e0862b000-2b4e0862c000 ---p 2b4e0862b000 00:00 0
2b4e0862c000-2b4e0872c000 rw-p 2b4e0862c000 00:00 0
2b4e0881c000-2b4e0881d000 r--p 0001c000 08:05 13389306 /lib64/ld-2.5.so
2b4e0881d000-2b4e0881e000 rw-p 0001d000 08:05 13389306 /lib64/ld-2.5.so
2b4e0881e000-2b4e08877000 r-xp 00000000 08:05 16704680 /usr/lib64/librpm-4.4.so
2b4e08877000-2b4e08a76000 ---p 00059000 08:05 16704680 /usr/lib64/librpm-4.4.so
2b4e08a76000-2b4e08a7c000 rw-p 00058000 08:05 16704680 /usr/lib64/librpm-4.4.so
2b4e08a7c000-2b4e08aae000 rw-p 2b4e08a7c000 00:00 0
2b4e08aae000-2b4e08bdb000 r-xp 00000000 08:05 13389214 /lib64/libcrypto.so.0.9.8e
2b4e08bdb000-2b4e08dda000 ---p 0012d000 08:05 13389214 /lib64/libcrypto.so.0.9.8e
2b4e08dda000-2b4e08dfb000 rw-p 0012c000 08:05 13389214 /lib64/libcrypto.so.0.9.8e
2b4e08dfb000-2b4e08dff000 rw-p 2b4e08dfb000 00:00 0
2b4e08dff000-2b4e08f32000 r-xp 00000000 08:05 16701685 /usr/lib64/libxml2.so.2.6.26
2b4e08f32000-2b4e09132000 ---p 00133000 08:05 16701685 /usr/lib64/libxml2.so.2.6.26
2b4e09132000-2b4e0913b000 rw-p 00133000 08:05 16701685

That renders the SNMPD daemon unusable.

Is everyone else having that particular problem?

I was helping myself by implementing a check script which runs once a minute and restarts "snmptrapd" and "snmpd" if there is no correct answer for a snmpget.

But this certainly cannot be the solution.

@Quantum: is this behaviour known or what can be done to have this fixed?

Thanks for your help.