From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0) Description of problem: On a clean install (both 7.0 and (another system) 7.3 updated with up2date) and no configuration changes starting the snmpd with /etc/init.d/snmpd start then running snmpwalk localhost public system results in output that stops after system.sysORTable.sysOREntry.sysORUpTime.8 = Timeticks: (16) 0:00:00.16 system.sysORTable.sysOREntry.sysORUpTime.9 = Timeticks: (16) 0:00:00.16 Timeout: No Response from localhost and the snmpd is found to be consuming lots of CPU time. The deamon must be restarted in order to get any further snmpwalk responses. The machines tested run as firewalls with two network cards. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.install ucd-snmp and ucd-snmp-utils 2.start snmpd with /etc/init.d/snmpd start 3.snmpwalk localhost public system Actual Results: Output stops after system.sysORTable.sysOREntry.sysORUpTime.8 = Timeticks: (16) 0:00:00.16 system.sysORTable.sysOREntry.sysORUpTime.9 = Timeticks: (16) 0:00:00.16 Timeout: No Response from localhost The snmpd is found to be consuming lots of CPU time. The deamon must be restarted in order to get any further snmpwalk responses. Expected Results: The 'system' OID tree should have been reported and the CPU demand released. Further requests should have been honoured by the deamon. Additional info: I have reported the local machine here. I have also installed 7.3 (updated with up2date) and get the same results on a similar firewall at a remote location. Both machines run as firewalls with two network cards. Otherwise they seem to be quite normal! I have run snmpd -D. I stopped the process when the log file had reached 320,000 lines.
Created attachment 67184 [details] Log file extract from snmp -D
*** This bug has been marked as a duplicate of 60161 ***