From owner-freebsd-stable@freebsd.org Tue Jul 5 08:38:39 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88515B206F3 for ; Tue, 5 Jul 2016 08:38:39 +0000 (UTC) (envelope-from freebsd@dohd.org) Received: from mx.terantula.net (mx.terantula.net [IPv6:2001:4cb8:1:3111::25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "*.terantula.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4AC4A1378 for ; Tue, 5 Jul 2016 08:38:39 +0000 (UTC) (envelope-from freebsd@dohd.org) Received: from mx.terantula.net (mx.terantula.nl [80.255.244.205]) by mx.terantula.net (Postfix) with ESMTP id E686F216F95 for ; Tue, 5 Jul 2016 10:38:26 +0200 (CEST) X-Virus-Scanned: amavisd-new at terantula.nl Received: from mx.terantula.net ([80.255.244.205]) by mx.terantula.net (mx.terantula.net [80.255.244.205]) (amavisd-new, port 10024) with LMTP id yiJOiQ0McYdN for ; Tue, 5 Jul 2016 10:38:24 +0200 (CEST) Received: from nala.dohd.org (nala.xs4all.nl [83.162.240.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.terantula.net (Postfix) with ESMTPS id C38B5216F94 for ; Tue, 5 Jul 2016 10:38:24 +0200 (CEST) Received: from mailscan.local.dohd.org (mailscan.local.dohd.org [10.0.0.205]) by nala.dohd.org (Postfix) with ESMTP id 823473AC8A for ; Tue, 5 Jul 2016 10:38:24 +0200 (CEST) X-Virus-Scanned: amavisd-new at dohd.org Received: from nala.dohd.org ([10.0.0.5]) by mailscan.local.dohd.org (mailscan.local.dohd.org [10.0.0.205]) (amavisd-new, port 10024) with LMTP id wU3Id-Kd0tY9 for ; Tue, 5 Jul 2016 10:38:23 +0200 (CEST) Received: by nala.dohd.org (Postfix, from userid 1008) id 995723AC83; Tue, 5 Jul 2016 10:38:23 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 nala.dohd.org 995723AC83 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dohd.org; s=_testsel; t=1467707903; bh=G81Vf/gHmGaSKGGKYKzr8N+Bed93f3vX7tQWnkoRs3Y=; h=Date:From:To:Subject:References:In-Reply-To; b=FeiaLoPXqsuLcM/HrpWstcYw8ILu3UIqVcv9L7ebgZP1pjBK0E5Zz0UfwOHHNVCt0 Z3f5UPP+pj59brUSu0iTWjEFciI3deAlRKLO6zCrbKC286KJYOeuYcYnYSz+O2xgmI 45I1JgQJpeLTVLlQKnOC3M7HmKPs4lsYNuxY05oA= Date: Tue, 5 Jul 2016 10:38:23 +0200 From: Mark Huizer To: freebsd-stable@FreeBSD.org Subject: Re: Recent stable: bsnmpd eats up memory and cpu Message-ID: <20160705083823.GA58223@eeyore.local.dohd.org> References: <20160501220107.GA58930@lyxys.ka.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160501220107.GA58930@lyxys.ka.sub.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2016 08:38:39 -0000 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...