From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Phil Oester <kernel@theoesters.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17 still croaks under heavy load
Date: Fri, 28 Dec 2001 12:01:45 +0200 [thread overview]
Message-ID: <20011228120145.G1072@mea-ext.zmailer.org> (raw)
In-Reply-To: <001101c18f6e$38b40160$6400a8c0@philxp>
In-Reply-To: <001101c18f6e$38b40160$6400a8c0@philxp>; from kernel@theoesters.com on Thu, Dec 27, 2001 at 11:06:50PM -0800
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.
Do you have RAID1 on the disks ?
Apparently "noapic" option helps, e.g. breaking the SYMMETRIC part of SMP.
You may also try "nmi_watchdog=1", if you have serial console attached
to the box for kernel message logging (and command).
> 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)
Yes, looks familiar. My hangups have been during high disc activity too.
My box is located into a place into which I have difficult access, e.g.
I can't use it to collect the debug data, and do magics (press reset)
to recover.
> I'd be more than willing to collect any other data required here, just
> let me know what would be of assistance. Note though that I only have
> remote access to this box, so getting magic sysrq info could be
> difficult/impossible (tho I do have console access if that helps).
>
> Thanks,
>
> Phil Oester
/Matti Aarnio
next prev parent reply other threads:[~2001-12-28 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 7:06 Phil Oester
2001-12-28 10:01 ` Matti Aarnio [this message]
2001-12-28 17:16 ` Phil Oester
2001-12-31 10:32 ` Florian Lohoff
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=20011228120145.G1072@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.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
Powered by JetHome