misc/18507: System 'dies' On High Load!!??
pres...@thecoolhost.com
>Number: 18507
>Category: misc
>Synopsis: System 'dies' On High Load!!??
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu May 11 16:00:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Shajan Alam
>Release: 4.0-RELEASE
>Organization:
TheCoolHost.com, Inc.
>Environment:
FreeBSD dell1.thecoolhost.com 4.0-RELEASE FreeBSD 4.0-RELEASE #0: Fri May 5 05:23:56 PDT 2000 ro...@dell1.themasterhost.com:/usr/src/sys/compile/MYKERNEL i386
>Description:
The system will stop responding during high loads (peak hours of the day with a busy website (2M+ pageviews/day))... The server should be able to handle it, considering its a Dell PowerEdge 4400 w/1GB RAM + 2x36GB Ultra3 SCSI HDs + Dual Intel EtherExpress PRO 100/B Network Cards... If I turn off apache (doesn't do me much good), the server is 100% fine, but if I turn on, it is dead in under 1 minute (this is a regular apache install, nothing special (./configure --prefix=/usr/local/apache)...)...
any ideas? (i tried apache 1.3.9 and 1.3.12, neither helped... hmm)
also, ram doesn't seem to 'unallocate?'... hmm... it just calls it inactive... but doesn't call it "free"... hmm... does that mean anything to you guys? (this is an output from the top of top after apache being off for about 15 minutes)
last pid: 62292; load averages: 0.00, 0.00, 0.00 up 2+06:34:30 20:47:01
32 processes: 1 running, 31 sleeping
CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle
Mem: 46M Active, 822M Inact, 96M Wired, 30M Cache, 55M Buf, 14M Free
>How-To-Repeat:
just get a busy website and turn on apache... and can't even ping server... after a few mins of this 'seemingly dead server' timing out ping requests, it comes back (about 7 mins)... and then i can quickly ssh in and 'killall -9 httpd', because if i don't, it dies again... hmm...
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Jeroen Ruigrok/Asmodai
From: Jeroen Ruigrok/Asmodai <asm...@wxs.nl>
To: pres...@thecoolhost.com
Cc: freebsd-gn...@FreeBSD.org
Subject: Re: misc/18507: System 'dies' On High Load!!??
Date: Sat, 13 May 2000 13:53:02 +0200
-On [20000512 04:00], pres...@thecoolhost.com (pres...@thecoolhost.com) wrote:
>
>also, ram doesn't seem to 'unallocate?'... hmm... it just calls it
>inactive... but doesn't call it "free"... hmm... does that mean
>anything to you guys? (this is an output from the top of top after
>apache being off for about 15 minutes)
Please read the manpage for top(1).
It would have explained you that this is the amount of memory allocated
to (In)active pages.
--
Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
Atone me to my throes curtail...
TheCoolHost, President
From: "TheCoolHost, President" <pres...@thecoolhost.com>
To: <freebsd-gn...@FreeBSD.org>, <pres...@thecoolhost.com>
Cc:
Subject: Re: misc/18507: System 'dies' On High Load!!??
Date: Sat, 13 May 2000 10:56:36 -0700
I think I may have stumbled on the problem/solution... Must increase the
MAXUSERS value in the kernel configuration... :)