> > > > Sounds like a data access problem. This is a killer bug (pun intended). > > I'm not seeing any crash here. > To my untrained eye it looks like its working. :-) >
But not in the intended way....:-( We should watch somewhat like : SNMPv2-SMI::enterprises.3495.1.4.1.1.1.64.233.183.99 = Gauge32: 7 SNMPv2-SMI::enterprises.3495.1.4.1.2.1.64.233.183.99 = Counter32: 11 SNMPv2-SMI::enterprises.3495.1.4.1.3.1.64.233.183.99 = Counter32: 0 Instead: SNMPv2-SMI::enterprises.3495.1.4.1.1.0 = Gauge32: 7 SNMPv2-SMI::enterprises.3495.1.4.1.2.0 = Counter32: 11 SNMPv2-SMI::enterprises.3495.1.4.1.3.0 = Counter32: 0 The reason , in var/logs/cache.log (debug_otions 49,9) 2007/11/21 09:34:50.214| snmpTreeNext: Recursed down to requested object 2007/11/21 09:34:50.214| snmpTreeNext: Attempting to recurse up for next object 2007/11/21 09:34:50.214| addr2oid: Dest : 2007/11/21 09:34:50.214| oid = .1.64.233.183.99 2007/11/21 09:34:50.214| snmp_meshPtblFn: peer 1 requested! 2007/11/21 09:34:50.214| oid2addr: id : 2007/11/21 09:34:50.214| oid = .1.0.8.139384744.1 2007/11/21 09:34:50.214| snmpAgentResponse: error. I will investigate... The error is around in oid2addr, or its callers. I'm very close...
