From owner-freebsd-questions@FreeBSD.ORG Fri May 13 13:15:56 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EF6616A4D0 for ; Fri, 13 May 2005 13:15:56 +0000 (GMT) Received: from mail25.sea5.speakeasy.net (mail25.sea5.speakeasy.net [69.17.117.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30B0F43D6B for ; Fri, 13 May 2005 13:15:56 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 12240 invoked from network); 13 May 2005 13:15:55 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail25.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 13 May 2005 13:15:55 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 23D2A30; Fri, 13 May 2005 09:15:53 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Ewald Jenisch References: <20050512085147.GA2114@aurora.oekb.co.at> From: Lowell Gilbert Date: 13 May 2005 09:15:53 -0400 In-Reply-To: <20050512085147.GA2114@aurora.oekb.co.at> Message-ID: <444qd7z2pi.fsf@be-well.ilk.org> Lines: 48 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: Tracking down "kern.ipc.maxpipekva exceeded" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2005 13:15:56 -0000 Ewald Jenisch writes: > Hi, > > For some time one of my machines in plaged be becoming completely > unresponsive after different amounts of time (several hours up to > several days). > > Symptoms: > Machine is PINGable, but no access over the network is possible > (neither ssh-login nor http-access). > > /var/log/messages: > May 11 12:11:00 io kernel: kern.ipc.maxpipekva exceeded; see tuning(7) > maxproc limit exceeded by uid 0, please see tuning(7) and login.conf(5). > (tons of both) > and finally > May 11 12:42:03 io kernel: maxproc > May 11 12:42:03 io kernel: limit exceede > May 11 12:42:03 io kernel: d by uid > May 11 12:42:03 io kernel: 0, ple > May 11 12:42:03 io kernel: se see tun > May 11 12:42:03 io kernel: ng(7) and l > May 11 12:42:03 io kernel: ogin.conf > May 11 12:42:03 io kernel: (5). > May 11 12:42:03 io kernel: > > >From that time on I can't log in any more, not even from the console. > > When rebooting the box via ctl-alt-del, before shutdown, it fails to > sync buffers on shutdown (counts down to 1 and stays there) and > finally gives up - requiring an fsck on reboot. > > Please note that the box does *not* crash completely, nor do I get a > kernel panic though. > > The system is running "5.4-STABLE FreeBSD 5.4-STABLE #0: Sat Apr 16 > 10:19:26 CEST 2005" but this problem has been there since I first > installed 5.3 on the box. > > So my primary question is: > > How do I track down the cause of the problem, i.e. which > program/process is responsible for "kern.ipc.maxpipekva" to be > exceeded? I would suggest keeping an eye on kern.ipc.pipekva and trying to correlate any changes to the activity on the system at the time.