From owner-freebsd-isp Wed Mar 11 14:40:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29150 for freebsd-isp-outgoing; Wed, 11 Mar 1998 14:40:08 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from wopr.inetu.net (wopr.inetu.net [207.18.13.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29115 for ; Wed, 11 Mar 1998 14:40:04 -0800 (PST) (envelope-from dev@wopr.inetu.net) Received: from localhost (dev@localhost) by wopr.inetu.net (8.8.5/8.8.5) with SMTP id RAA06767 for ; Wed, 11 Mar 1998 17:52:13 -0500 (EST) Date: Wed, 11 Mar 1998 17:52:13 -0500 (EST) From: Dev To: isp@FreeBSD.ORG Subject: Runaway web server. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We have a freebsd 2.2.5 server w/96 megs of ram running 13 instances of apache. (each spawning about 5-10 children). it seems something triggers _all_ of the servers to become in the run state. about 4 or 5 children seem to be using about 8 mb of ram. it is very hard to actually kill the processes. (not just from lag, but the process not dying after being sent a kill signal). when trying to kill the session leader it does not seem to die. The servers get stuck in a "waiting for reply" state and never seem to respond. This server has been up for over 40 days running fine. We have finally rebooted the machine, and after about four hours it happened again. Anyone have any suggestions? Dev Chanchani - INetU, Inc.(tm) - http://www.INetU.net Electronic commerce - Web development - Web hosting dev@INetU.net - Phone: (610) 266-7441 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message