From owner-freebsd-questions@FreeBSD.ORG Tue Jan 6 07:31:20 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DA96106566B for ; Tue, 6 Jan 2009 07:31:20 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 08FEF8FC18 for ; Tue, 6 Jan 2009 07:31:19 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id B0435AFC1FF; Mon, 5 Jan 2009 22:31:18 -0900 (AKST) From: Mel To: freebsd-questions@freebsd.org Date: Mon, 5 Jan 2009 22:05:06 -0900 User-Agent: KMail/1.9.10 References: <200901051529.n05FTXOr044399@phoenix.panhistoria.com> In-Reply-To: <200901051529.n05FTXOr044399@phoenix.panhistoria.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901052205.06298.fbsd.questions@rachie.is-a-geek.net> Cc: Sydney Longfellow Subject: Re: Processes Piling up with the lockf state X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2009 07:31:20 -0000 On Monday 05 January 2009 06:29:33 Sydney Longfellow wrote: > I'm getting problems with my server locking up after accumulating far > too many processes until I have to reboot. > > The states of the processes are reading either sbwait or lockf when this > spiral out of control starts to happen. > > Any ideas what might cause this? sbwait indicates a process is waiting for data on a socket. lockf indicates that a process is trying to lock portions of a file. If you put the two together, a cause could be network congestion (disk to network) or harddrive problems (network to disk). A server running out of memory and into swap can also be a cause, as processes are blocked (sockets don't get data and locks are not acquired) until the swap operation is completed. When processes keep getting spawned, this effect snowballs. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.