ports/66247: snmpd exits with signal 10

Holger Kipp hk at alogis.com
Tue May 4 10:30:42 UTC 2004


>Number:         66247
>Category:       ports
>Synopsis:       snmpd exits with signal 10
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue May 04 03:30:37 PDT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Holger Kipp
>Release:        5.2-CURRENT
>Organization:
alogis AG
>Environment:
FreeBSD www.customer.com 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Tue May  4 11:17:16 CEST 2004     root at www.customer.com:/usr/obj/usr/src/sys/WWW_SMP_5  i386
>Description:
Calling "snmpwalk -c public -v2c 127.0.0.1" several times (or from the remote system doing the monitoring) will result in the following error:

kernel: pid 82705 (snmpd), uid 0: exited on signal 10 (core dumped)

snmpwalk will stop outputting values and says
"Timeout: No Response from 127.0.0.1" instead.


This happens with

ucd-snmp-4.2.6_3
net-snmp-5.1
net-snmp-5.1.1_1

on FreeBSD 5-CURRENT (yesterday, today). No problems with ucd-snmp-4 on FreeBSD 4.7-STABLE. We are just in the process of preparing an upgrade, that's why we noticed this at all.
>How-To-Repeat:
Install a FreeBSD 5-CURRENT and net-snmp-5, configure snmp for reading and issue "snmpwalk -c public -v2c 127.0.0.1" a few times (eg up to 10 or 20).
>Fix:
      
>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list