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
Created attachment 73064 [details] Excerpt from /var/log/messages
*** This bug has been marked as a duplicate of 60161 ***