From: Florian Lohoff <flo@rfc822.org>
To: Phil Oester <kernel@theoesters.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17 still croaks under heavy load
Date: Mon, 31 Dec 2001 11:32:39 +0100 [thread overview]
Message-ID: <20011231103239.GA18933@paradigm.rfc822.org> (raw)
In-Reply-To: <001101c18f6e$38b40160$6400a8c0@philxp>
In-Reply-To: <001101c18f6e$38b40160$6400a8c0@philxp>
[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]
On Thu, Dec 27, 2001 at 11:06:50PM -0800, Phil Oester wrote:
> Have a webserver running Zope (specifically the ZEO db) which dies every
> few days with no messages in syslog. Locks up so tight a powercycle is
> required to recover. System has 1gb RAM, 2xSMP, kernel configured with
> 4gb highmem.
>
> Since the kernel doesn't provide any info in syslog when it dies, I just
> ran a vmstat 30 to a file and waited for the next untimely demise.
> Here's what happened when it died last time. Note the sudden surge in
> disk activity (bi)
I am seeing the same kind of deaths on multiple very different SMP boxes
since 2.2 days. They do not die in the "high load" case but only the
high load boxes are unstable. I am having on "testcase" where the box
crashes at least every 24 hours (mutella). Boxes i have seen this
happening on are
Box1:
Dual Celeron 400
IDE Raid
SCSI System disk
1GB Ram (No Highmem) (Used to have 512M)
EEPro 100
Box2:
Dual PIII 1Ghz
Serverworks Board
1GB Ram (No Highmem)
ICP Vortex Raid
EEPro 100
I have 3 machines of the exakt same type of the latter type. All are
unstable and tend to crash depending on application every 24 hours to
every 2-3 Weeks.
No notice in the syslog, nothing on the serial console. There are
completly dead without any sign before. I have tried to capture
informations about processes, swap, memory etc - Within 1 minute
prior to crash the boxes are basically idle.
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Nine nineth on september the 9th Welcome to the new billenium
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-12-31 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 7:06 2.4.17 still croaks under heavy load Phil Oester
2001-12-28 10:01 ` Matti Aarnio
2001-12-28 17:16 ` Phil Oester
2001-12-31 10:32 ` Florian Lohoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-29 2:20 Dieter Nützel
2001-12-29 2:57 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011231103239.GA18933@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=kernel@theoesters.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox