From owner-freebsd-isp Wed Jun 5 10:29:44 2002 Delivered-To: freebsd-isp@freebsd.org Received: from coloradosurf.com (12-253-160-7.client.attbi.com [12.253.160.7]) by hub.freebsd.org (Postfix) with ESMTP id 697D737B405 for ; Wed, 5 Jun 2002 10:29:41 -0700 (PDT) Received: (from mike@localhost) by coloradosurf.com (8.11.6/8.11.6) id g55HTcO55435 for freebsd-isp@freebsd.org; Wed, 5 Jun 2002 11:29:38 -0600 (MDT) (envelope-from mike) Date: Wed, 5 Jun 2002 11:29:38 -0600 From: Mike To: freebsd-isp@freebsd.org Subject: apache eating up swap Message-ID: <20020605112938.D55224@coloradosurf.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hope this isn't too OT, not sure if it's specific to FreeBSD or not (I found both suggestions in searches). I'm running Apache/1.3.22 (Unix) PHP/4.0.6 mod_ssl/2.8.5 OpenSSL/0.9.6b on FreeBSD 3.5S. My webserver appears to use more and more swap as time goes by. I've watched this via top and swapinfo. Graceful restarts take care of things (frees up my swap). If no restart is issued, apache will continue to eat up all swap and all other processes have no memory to work with (choke --> die). I've been lucky enough to spot it and restart before a full server crash (I've heard this will happen). I find nothing in the logs. I moved one of our 'heavy users' to another box and the problem all but disappeared. I have a program running now that monitors my swap and restarts apache, but clearly, that is not the best solution. The site I moved did have some good sized http file downloads (if that helps any other diagnostician). Sure does act like a memory leak. Grateful for any clues. TIA, mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message