Date: Tue, 04 May 2004 16:09:56 +0000 From: Holger Kipp <Holger.Kipp@alogis.com> To: amon@sockar.homeip.net Cc: kuriyama@freebsd.org Subject: Re: net-snmp dies with signal 10 on 5-CURRENT Message-ID: <200405041610.i44GA1b00907@alogis.com>
next in thread | raw e-mail | index | archive | help
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...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405041610.i44GA1b00907>