Bug 72681

Summary: snmpd handles get-next poorly
Product: [Retired] Red Hat Linux Reporter: l0cksley
Component: ucd-snmpAssignee: Phil Knirsch <pknirsch>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-08-26 16:40:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Excerpt from /var/log/messages none

Description l0cksley 2002-08-26 16:37:34 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461)

Description of problem:
With the default configuration which restricts access
to the system branch only, issuing a get-next at the
end of the branch causes snmpd to spew modprobe and
/proc/stat messages in /var/log/messages,
use 100% CPU and stop responding for several minutes.
This does not occur with looser access restrictions.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. snmpgetnext localhost public .1.3.6.1.2.1.1.9.1.4.9
2.
3.
	

Actual Results:  Timeout: No Response from localhost

Expected Results:  End of MIB

Additional info:

ucd-snmp-4.2.5-7.73.0
Comment 1 l0cksley 2002-08-26 16:40:26 UTC 
Created attachment 73064 [details]
Excerpt from /var/log/messages
Comment 2 Phil Knirsch 2002-08-28 13:45:37 UTC 

*** This bug has been marked as a duplicate of 60161 ***