From owner-freebsd-stable@FreeBSD.ORG Fri Dec 10 22:03:16 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D730016A4CE for ; Fri, 10 Dec 2004 22:03:16 +0000 (GMT) Received: from brugere.aub.dk (fw.aub.dk [195.24.1.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id C52D843D54 for ; Fri, 10 Dec 2004 22:03:11 +0000 (GMT) (envelope-from techlists@motrix.dk) Received: by brugere.aub.dk (Postfix, from userid 1858) id 095E9C466; Fri, 10 Dec 2004 23:03:10 +0100 (CET) Received: from proxy.aub.dk (proxy.aub.dk [10.10.10.12]) by mail.aub.dk (IMP) with HTTP for ; Fri, 10 Dec 2004 23:03:09 +0100 Message-ID: <1102716189.41ba1d1ddfd03@mail.aub.dk> Date: Fri, 10 Dec 2004 23:03:09 +0100 From: "J. Martin Petersen" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 X-Originating-IP: 10.10.10.12 Subject: netstat fails with memory allocation error and error in kvm_read X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 22:03:16 -0000 Hi We are trying to gather some debug information for a problem that is difficult to diagnose, as the machine always ends up hard frozen (does not do anything, can not break to debugger, does not respond to keyboard, etc.), so we are dumping output from netstat, vmstat, iostat etc. quite often. The cron jobs fail ever so often with error messages I do not quite understand, and I can not find anything relevant in the archives. Can anyone shed some light on this? Command: netstat -r Error message: netstat: kvm_read: Bad address Debug before: http://www.aub.dk/~jmp/fw/debug-2004.12.09-21.34.41.gz Debug after: http://www.aub.dk/~jmp/fw/debug-2004.12.09-21.35.06.gz # errors: 7 Command: netstat -an Error message: netstat: sysctl: net.inet.udp.pcblist: Cannot allocate memory Debug before: http://www.aub.dk/~jmp/fw/debug-2004.12.09-07.38.48.gz Debug after: http://www.aub.dk/~jmp/fw/debug-2004.12.09-07.39.04.gz # errors: 3 Command: netstat -an Error message: netstat: sysctl: net.inet.raw.pcblist: Cannot allocate memory Debug before: http://www.aub.dk/~jmp/fw/debug-2004.12.10-22.19.50.gz Debug after: http://www.aub.dk/~jmp/fw/debug-2004.12.10-22.20.10.gz # errors: 6 The number of errors are in the last five days. Kernelconfig (FIREWALL), dmesg, pf.conf etc. can be found at http://www.aub.dk/~jmp/fw/ The commands we are running are: netstat -i, netstat -m, netstat -s, netstat -an, netstat -r vmstat, vmstat -i, vmstat -f, vmstat -m, vmstat -z iostat ps waux every 15 seconds. We are running the same commands (plus pfctl -vvsa) from root's cron every minute. The hard lockups seems to be connected to our use of pf and altq, that is at least the problem we're trying to gather debug information for. Thanks in advance Martin