Here is the last few lines of snmpwalk when it dies. TCP-MIB::tcpCurrEstab.0 = Gauge32: 0 TCP-MIB::tcpInSegs.0 = Counter32: 5700389 TCP-MIB::tcpOutSegs.0 = Counter32: 8082775 TCP-MIB::tcpRetransSegs.0 = Counter32: 94 TCP-MIB::tcpConnState.0.0.0.0.0.0.0.0.0.0 = INTEGER: listen(2) TCP-MIB::tcpConnState.172.30.217.212.22.172.30.209.150.1947 = INTEGER: listen(2) TCP-MIB::tcpConnState.172.30.217.212.22.172.30.209.150.1948 = INTEGER: listen(2) TCP-MIB::tcpConnState.172.30.217.212.23.172.30.209.130.2721 = INTEGER: listen(2) TCP-MIB::tcpConnState.172.30.217.212.1667.172.30.217.220.23 = INTEGER: listen(2) TCP-MIB::tcpConnLocalAddress.0.0.0.0.0.0.0.0.0.0 = IpAddress:
I ran snmpgetnext and snmpd immediately dies. Snmpgetnext timesout. David -----Original Message----- From: Dave Shield [mailto:[EMAIL PROTECTED] Sent: Thursday, March 02, 2006 12:19 PM To: Pike, David Cc: Thomas Anders; [email protected] Subject: RE: snmpwalk kills snmpd-5.3.0.1 on TRU64 On Thu, 2006-03-02 at 10:25 -0500, Pike, David wrote: > > The obvious question then is: what if you do *not* apply your patch, > > rebuild without the "host" mib module and snmpwalk again? Does it > > still crash? > > It still dies. What's the last value that it returns before dying? What happens if you restart the agent, and then run a single "snmpgetnext" request on this OID? I'd suggest doing this with '-r 0 -t 60', to avoid problems with the agent being swamped with repeated retries. Dave ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
