From owner-freebsd-hackers Thu Aug 30 11:46:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id AAAA537B40D for ; Thu, 30 Aug 2001 11:46:45 -0700 (PDT) (envelope-from dphoenix@bravenet.com) Received: (qmail 7978 invoked by uid 1001); 30 Aug 2001 18:55:45 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Aug 2001 18:55:45 -0000 Date: Thu, 30 Aug 2001 11:55:45 -0700 (PDT) From: Dan To: mark tinguely Cc: Subject: Re: memory + apache In-Reply-To: <200108301719.f7UHJtR51738@web.cs.ndsu.nodak.edu> Message-ID: <20010830113325.E6569-100000@gandalf.bravenet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I will give it a try. touch /var/account/acct accton how long does it take for anything to get written to that file? As far as fork storms, I did noticed 1. I had the junior admin write a script to restart apache if LA got to high ....doing a truss on the pid i did noticed mad processes and his perl script hitting 10% cpu at times. Looking at it it was just a basic infinite while loop checking `uptime`. I have taken that script off but I don;t think that is what is causing this swap issue. Checking the hardware as well I have confirmed that the manufacter for these machines only included a heat sink and this tiny fan not big enough for these boxes....so cooling of the chip may be an issue as well.....gonna have to check over a bunch of things next couple days. On Thu, 30 Aug 2001, mark tinguely wrote: > Date: Thu, 30 Aug 2001 12:19:55 -0500 (CDT) > From: mark tinguely > To: dphoenix@bravenet.com, tinguely@web.cs.ndsu.nodak.edu > Cc: freebsd-hackers@FreeBSD.ORG > Subject: Re: memory + apache > > > > Yeah that is what I am thinking to. My guess is some large array allocated > > in the php code maybe or a sql query taking to long to finish eating up > > all the ram. That is kind of interesting to know. > > you said that the CPU usage spikes also at the time of the memory depletion? > I wonder if you have some fork storm. If you had process accounting > enabled and match it up with the web log file and vmstat activity you > may be able to narrow your search. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message