RE: problems with 1.2b22 snmp

Yip, you found a bug, just writing a patch for this. It is an ugly little
bugger :-)

Glenn

-----Original Message-----
From: Jordan Mendelson [mailto:jordy@wserv.com]
Sent: Monday, June 29, 1998 2:10 PM
To: squid-users@ircache.net
Subject: problems with 1.2b22 snmp

Just having some odd problems.. I'm using CMU's snmpwalk to query the
server. I changed the server's default port to 161 so I wouldn't have to
much around with mrtg (since I use it to query routers as well). I also
changed the default community.

Anyhow, this is what I get when I query it with no objects:

system.sysDescr = "1.2.beta22"
system.sysObjectID = Wrong Type (should be OBJECT IDENTIFIER): "1.2.beta22"
system.sysUpTime = Timeticks: (1126) 0:00:11
system.sysContact = "iocache-1.wserv.com"

Now, it will crash if I do:

# snmpwalk iocache-1.wserv.com labtec .1.3.6.1.3.25.17.4.4

debugging shows:

1998/06/29 01:54:48| snmpHandleUdp: Called.
1998/06/29 01:54:48| snmpHandleUdp: FD 36: received 44 bytes from
206.105.188.2.
1998/06/29 01:54:48| snmpAgentParse: reqid=[1]
1998/06/29 01:54:48| snmpAclCheckDone: 1
1998/06/29 01:54:48| snmpCommunityCheck: labtec against:
1998/06/29 01:54:48| oid = .1.3.6.1.3.25.17.4.4
1998/06/29 01:54:48| snmpViewCheck: called with index=2
1998/06/29 01:54:48| snmpViewCheck: found view for subtree:
1998/06/29 01:54:48| oid = .1.3.6
1998/06/29 01:54:48| snmpAclCheckDone: done checking communities.
1998/06/29 01:54:48| snmpAgentResponse: Received a 161 PDU
1998/06/29 01:54:48| oidlist_Next: Looking for next of:
1998/06/29 01:54:48| oid = .1.3.6.1.3.25.17.4.4
1998/06/29 01:54:48| oidlist_Next: Passed mib. Checking this one.
FATAL: Received Segment Violation...dying.

When I try to query another OID, it won't return any information at all, for
example:

# snmpwalk iocache-1.wserv.com labtec .1.3.6.1.3.25.17.3.2.1.11

returns nothing, and the logs read:

1998/06/29 02:08:27| snmpHandleUdp: Called.
1998/06/29 02:08:27| snmpHandleUdp: FD 34: received 46 bytes from
206.105.188.2.
1998/06/29 02:08:27| snmpAgentParse: reqid=[1]
1998/06/29 02:08:27| snmpAclCheckDone: 1
1998/06/29 02:08:27| genericGetNextFn: Adding missing information.
1998/06/29 02:08:27| snmp_prfProtoFn: Processing request with magic 2!
1998/06/29 02:08:27| Buffer=81dceb8 BufLenP=83f8bec, buflen=4096
1998/06/29 02:08:27| snmpAclCheckDone: ok ret=0!
1998/06/29 02:08:27| snmpAgentParseDone: errstat=1, reqid=0 _t=83f8bd8
1998/06/29 02:08:27| snmp: parsed.
1998/06/29 02:08:27| snmpUdpSend: Queueing response for 206.105.188.2
1998/06/29 02:08:28| snmpUdpReply: FD 34 sending 52 bytes to 206.105.188.2
port 1273
1998/06/29 02:08:28| snmpUdpReply: freeing 0x81dceb8
1998/06/29 02:08:28| snmpUdpReply: freeing 0x81d7910

My configuration is:

snmp_port 161
snmp_do_queueing on
snmp_mib_path /usr/local/squid/etc/mib.txt
snmp_trap_community labtec

snmp_agent_conf view all .1.3.6 included
snmp_agent_conf view squid .1.3.6 included
snmp_agent_conf user squid - all all labtec
snmp_agent_conf user all all all all squid
snmp_agent_conf community labtec squid squid
snmp_agent_conf community readwrite all all

snmp_acl labtec allow secure
snmp_acl labtec deny all

Any clues? I'm just trying to monitor it with mrtg :)

Jordan

--
Jordan Mendelson     : http://jordy.wserv.com
Web Services, Inc.   : http://www.wserv.com