From owner-freebsd-stable Mon Mar 29 2:41:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from diamond.ripn.net (diamond.ripn.net [195.19.26.76]) by hub.freebsd.org (Postfix) with ESMTP id 8E0131581E for ; Mon, 29 Mar 1999 02:41:32 -0800 (PST) (envelope-from ilya@diamond.ripn.net) Received: (from ilya@localhost) by diamond.ripn.net (8.9.2/8.9.2) id OAA46425 for freebsd-stable@freebsd.org; Mon, 29 Mar 1999 14:40:50 +0400 (MSD) (envelope-from ilya) Message-Id: <199903291040.OAA46425@diamond.ripn.net> Subject: kvm_read: Bad address (ucd-snmp; fbsd 3.1-stable) To: freebsd-stable@freebsd.org Date: Mon, 29 Mar 1999 14:40:50 +0400 (MSD) From: Ilya Varlashkin X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Recently I've moved from 2.2-stable to 3.1-stable. I've noticed snmpd (compiled after 3.1-stable installed) now crashes upon every snmpwalk. Actualy snmpd continuously writes to snmpd.log as follow /var partition becomes full. Looked in log file I've found following: kvm_read(*, 9a0, 0xefbfb8b4, 96) = 0: kvm_read: Bad address TCP_Count_Connections - inpcb: Bad address kvm_read(*, 9a0, 0xefbfb8b4, 96) = 0: kvm_read: Bad address TCP_Count_Connections - inpcb: Bad address kvm_read(*, 9a0, 0xefbfb8b4, 96) = 0: kvm_read: Bad address TCP_Count_Connections - inpcb: Bad address (About 58MB total for one pass of snmpwalk) Any clue on whether is it UCD-SNMP port fault or FreeBSD core problem? -- Ilya Varlashkin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message