From owner-freebsd-current@FreeBSD.ORG  Tue May  4 09:10:15 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 920A616A4CE; Tue,  4 May 2004 09:10:15 -0700 (PDT)
Received: from alogis.com (firewall.solit-ag.de [212.184.102.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B39C043D31; Tue,  4 May 2004 09:10:13 -0700 (PDT)
	(envelope-from Holger.Kipp@alogis.com)
Received: from intserv.int1.b.intern (localhost [127.0.0.1])
	by alogis.com (8.11.1/8.9.3) with SMTP id i44GA1b00907;
	Tue, 4 May 2004 18:10:01 +0200 (CEST)
	(envelope-from hk@alogis.com)
Message-Id: <200405041610.i44GA1b00907@alogis.com>
Date: Tue, 04 May 2004 16:09:56 +0000
From: Holger Kipp <Holger.Kipp@alogis.com>
To: amon@sockar.homeip.net
X-Mailer: phpGroupWare (http://www.phpgroupware.org)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-description: Mail message body
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
Reply-To: Holger.Kipp@alogis.com
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 May 2004 16:10:15 -0000



amon@sockar.homeip.net (amon@sockar.homeip.net) wrote: 

>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.

>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 :

Hmm, I don't get any messages about memory that can't be allocated, just the
"kernel: pid 66673 (snmpd), uid 0: exited on signal 10"

>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)

Behaviour is easily reproducible here. It is on HP ProLiant DL360 G3 with dual
Xeon processors, system is completely idle...