Date: Wed, 21 Dec 2016 15:07:04 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 215471] Using bsnmpd with the snmp_hostres module on a vmware ESXi guest with a disconnected CD drive uses 100% CPU Message-ID: <bug-215471-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215471 Bug ID: 215471 Summary: Using bsnmpd with the snmp_hostres module on a vmware ESXi guest with a disconnected CD drive uses 100% CPU Product: Base System Version: 11.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: jimp@pfsense.org CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Created attachment 178177 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=178177&action=edit A configuration file for bsnmpd which can reproduce the high CPU usage problem on a vmware guest When running FreeBSD 11.0-RELEASE (from release until at least -p5), there is a combination of factors that leads to bsnmpd using 100% CPU. It seems to require all of the following: * FreeBSD 11 running as a guest in VMWare ESXi * The guest has a "CD/DVD Drive" listed in its hardware on ESX * The CD/DVD Drive is in a disconnected state * The snmp_hostres module is loaded in the bsnmpd configuration file * bsnmpd enabled and running Here is a very small snmpd.config that can replicate the problem in a similar environment: ================== %snmpd sysDescr = "FreeBSD doctor.example.com FreeBSD 11.0-RELEASE-p5 amd64" begemotSnmpdCommunityString.0.1 = "supersecret" begemotSnmpdPortStatus.0.0.0.0.161 = 1 begemotSnmpdModulePath."mibII" = "/usr/lib/snmp_mibII.so" begemotSnmpdModulePath."hostres" = "/usr/lib/snmp_hostres.so" ================== If bsnmpd is run on this guest with that configuration, it consumes all available CPU. I'll attach the above snmpd.config, along with top output and a sample of the truss output taken while bsnmpd was running. Currently the only workaround is to disable the hostres module, but that means losing access to any of the information it provides. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215471-8>