From owner-freebsd-current@FreeBSD.ORG Tue May 4 07:43:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5872B16A4CE; Tue, 4 May 2004 07:43:40 -0700 (PDT) Received: from sockar.homeip.net (tourist.net1.nerim.net [62.212.109.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 319B543D5E; Tue, 4 May 2004 07:43:39 -0700 (PDT) (envelope-from amon@sockar.homeip.net) Received: from sockar.homeip.net (localhost [127.0.0.1]) by sockar.homeip.net (8.12.9p2/8.12.9) with ESMTP id i44EftJL069022; Tue, 4 May 2004 16:41:55 +0200 (CEST) (envelope-from amon@sockar.homeip.net) Received: (from amon@localhost) by sockar.homeip.net (8.12.9p2/8.12.9/Submit) id i44Eft6M069021; Tue, 4 May 2004 16:41:55 +0200 (CEST) (envelope-from amon) Date: Tue, 4 May 2004 16:41:55 +0200 From: amon@sockar.homeip.net To: Holger Kipp Message-ID: <20040504164155.E34673@ra.aabs> References: <200405041046.i44Akbb87907@alogis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5.1i In-Reply-To: <200405041046.i44Akbb87907@alogis.com>; from Holger.Kipp@alogis.com on Tue, May 04, 2004 at 10:46:32AM +0000 cc: current@freebsd.org cc: kuriyama@freebsd.org Subject: Re: net-snmp dies with signal 10 on 5-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2004 14:43:40 -0000 Le 04/05/2004 à 10:46, Holger Kipp a écrit: > net-snmp (both 4 and 5) die after being called several times > > snmpwalk -c public -v2c 127.0.0.1 > > with signal 10. > this is with 5-CURRENT (no problems with same configuration on 4.7-STABLE). > > PR is ports/66247. > > anyone else is seeing this? I installed the net-snmpd-5.1.1 port on a sparc64 system running current from April 26 a few days ago and also got a SIGBUS in snmpd when it was polled by our rrdtool. I got the following message in the logs but don't know if it is related or not to the crash : Apr 30 01:07:22 kellthuzad snmpd[66673]: sysctl: physmem: Cannot allocate memory pid 66673 (snmpd), uid 0: exited on signal 10 (core dumped) Apr 30 01:13:48 kellthuzad kernel: pid 66673 (snmpd), uid 0: exited on signal 10 (core dumped) Apr 30 02:50:31 kellthuzad snmpd[67417]: sysctl: physmem: Cannot allocate memory The error seems to come from a failed call to sysctl(). The snmpd has not crashed again since that date (it's still polled every 5 min) Hope this helps. -- Herve Boulouis