From owner-freebsd-ports Mon Mar 18 9:50:20 2002 Delivered-To: freebsd-ports@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A240C37B405 for ; Mon, 18 Mar 2002 09:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2IHo0m82107; Mon, 18 Mar 2002 09:50:00 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C219C37B404 for ; Mon, 18 Mar 2002 09:40:43 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2IHehY80773; Mon, 18 Mar 2002 09:40:43 -0800 (PST) (envelope-from nobody) Message-Id: <200203181740.g2IHehY80773@freefall.freebsd.org> Date: Mon, 18 Mar 2002 09:40:43 -0800 (PST) From: Steve Shorter To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: ports/36054: snmpd daemon from ucd-snmp-4.2.3 crashes Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 36054 >Category: ports >Synopsis: snmpd daemon from ucd-snmp-4.2.3 crashes >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Mar 18 09:50:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Steve Shorter >Release: FreeBSD 4.5 i386 >Organization: >Environment: FreeBSD jak 4.5-STABLE FreeBSD 4.5-STABLE #0: Sat Mar 16 07:54:07 EST 2002 root@jak:/usr/src/sys-stable.2002_02_21/compile/JAK i386 >Description: snmpd crashes and logs error on machine boot/startup or after repeated queries from clients. Occurs on several machines of differing hardware and configuration. Crashes appear to be unpredictable but same error is logged. Mar 17 13:45:07 <1.6> cgi2 /kernel: pid 139 (snmpd), uid 69: exited on signal 11 Mar 17 13:45:07 <3.3> cgi2 ucd-snmp[139]: kvm_read(*, 0, 0x280cbd04, 4) = -1: kvm_read: Bad address Mar 17 13:45:07 <3.3> cgi2 ucd-snmp[139]: auto_nlist failed on boottime at location 0 Mar 17 13:45:07 <3.3> cgi2 ucd-snmp[139]: kvm_read(*, 0, 0x280cbd04, 4) = -1: kvm_read: Bad address Mar 17 13:45:07 <3.3> cgi2 ucd-snmp[139]: auto_nlist failed on boottime at location 0 Mar 17 13:45:07 <3.3> cgi2 ucd-snmp[139]: kvm_read(*, 0, 0x280cbd04, 4) = -1: kvm_read: Bad address Mar 17 13:45:07 <3.3> cgi2 ucd-snmp[139]: auto_nlist failed on boottime at location 0 Mar 17 13:45:07 <3.3> cgi2 ucd-snmp[139]: kvm_read(*, 0, 0x280cc1c0, 196) = -1: kvm_read: Bad address Mar 17 13:45:07 <3.3> cgi2 ucd-snmp[139]: auto_nlist failed on cnt at location 0 Mar 17 18:08:39 <3.3> cgi2 ucd-snmp[137]: kvm_read(*, 2f74736f, 0x280cc1c0, 196) = -1: kvm_read: Bad address Mar 17 18:08:39 <3.3> cgi2 ucd-snmp[137]: auto_nlist failed on cnt at location 2f74736f >How-To-Repeat: Problem behavior is not 100% predictable but happens more frequently on bootup, but also occurs after varying uptimes. ucp-snmp 4.2 did not exhibit this problem >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message