From: fire-eyes <sgtphou@fire-eyes.org>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Server goes down twice in two days, looking for input
Date: Fri, 23 Sep 2005 13:48:52 -0400 [thread overview]
Message-ID: <43344004.6000601@fire-eyes.org> (raw)
In-Reply-To: <20050923161421.GD8371@gentoo.org>
Sven Vermeulen wrote:
> On Thu, Sep 22, 2005 at 10:34:06AM -0400, fire-eyes wrote:
>
>>I have had our gentoo server go down twice in under two days. I am
>>currently trying to figure out what is happening.
>
>
> What did you do before this behavior started? Any kernel upgrades? You might
> want to consider downgrading and checking if that fixes the problem.
>
> Try running any system monitoring processes in the future that monitor,
> amongst other things, CPU usage and I/O. It might help locating the source
> of the problems.
There was a kernel upgrade but that was over three months ago. I have
tried to replicate the situation (it went down both times when I was
creating a tar.bz2) without luck.
I'm thinking of installing an snmpd and then perhaps cacti or similar on
another system to poll and keep histories of various data. That's a
good idea.
--
gentoo-server@gentoo.org mailing list
prev parent reply other threads:[~2005-09-23 17:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 14:34 [gentoo-server] Server goes down twice in two days, looking for input fire-eyes
2005-09-22 15:46 ` Yogesh Sharma
2005-09-22 15:54 ` fire-eyes
2005-09-22 16:25 ` Yogesh Sharma
2005-09-22 16:29 ` fire-eyes
2005-09-22 16:53 ` Yogesh Sharma
2005-09-22 16:58 ` fire-eyes
2005-09-22 15:57 ` A. Khattri
2005-09-22 16:07 ` fire-eyes
2005-09-22 17:01 ` Robert Larson
2005-09-22 17:57 ` fire-eyes
2005-09-23 16:14 ` Sven Vermeulen
2005-09-23 17:48 ` fire-eyes [this message]
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=43344004.6000601@fire-eyes.org \
--to=sgtphou@fire-eyes.org \
--cc=gentoo-server@lists.gentoo.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