Date: Tue, 5 Jul 2016 10:38:23 +0200 From: Mark Huizer <freebsd+stable@dohd.org> To: freebsd-stable@FreeBSD.org Subject: Re: Recent stable: bsnmpd eats up memory and cpu Message-ID: <20160705083823.GA58223@eeyore.local.dohd.org> In-Reply-To: <20160501220107.GA58930@lyxys.ka.sub.org> References: <20160501220107.GA58930@lyxys.ka.sub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 02, 2016 at 12:01:07AM +0200, Wolfgang Zenker wrote: > Hi, > > after updating some 10-STABLE systems a few days ago, I noticed that on > two of those systems bsnmpd started to use up a lot of cpu time, and the > available memory shrinked until rendering the system unusable. Killing > bsnmpd stops the cpu usage but does not free up memory. > Both affected systems are amd64, one having moved from r297555 to > r298723, the other from r297555 to r298722. Another amd64 system > that went from r297555 to r298722 appears to be not affected. > The two affected systems are on an internal LAN segment and there > is currently no application connecting to snmp on those machines. > > What would be useful debugging data to collect in this case? I saw a resembling thing here after upgrading to 10-stable yesterday. I noticed bsnmp running at 30 to 40% cpu continuously, resembling what I found here: https://forums.freebsd.org/threads/37045/ After ktrace-ing the process I noticed it was doing sysctl stuff all the time and a more close look showed that it was freaking out on the CD device without a medium. So I inserted a CD in the device, and bsnmp went back to normal. "Interesting". So far I didn't notice memory issues. Mark -- Nice testing in little China...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160705083823.GA58223>