[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] Crashing Problems



> Date: Wed, 17 Apr 2002 03:00:31 +0100
> From: ISEE Multimedia <mail@xxxxxxxxxxxxxxxxxxx>

[ somewhat snipped ]


> My server crashed a few times yesterday, and i think it was a
> memory issue.

Memory, power, overheating, or perhaps hard drive [controller]
are all possible culprits... assuming that it is indeed hardware.


> What logs/commands can i view/execute to find out which site or
> program caused the memory error or crash. Or just the crash?

Define "crash".

You might be able to detect hard drive errors directly in the
kernel logs.  If a random memory error is causing panics, the
console is the place to be.

BSD process accounting might help, but is by no means a magic
silver bullet.  (I also don't recall if it's compiled into the
RaQ kernel by default... I guess I _could_ whip up a program to
test if anyone is interested in this approach...)

Attempting to say "which site or program caused the memory error
or crash" is likely arbitrary and futile:  An unstable system
will often strike randomly, and at the kernel level.

Note that a large compile (kernel, gcc, glibc) with a high number
of max_jobs will often tickle enough things to anger a flaky
system.  If one gets weird errors during such compiles, suspect a
hardware error.

Whatever you do, I'd recommend some console viewing.  Any way to
connect to con while you 1) hunt gremlins or 2) sit back and
watch or log?


> Thanks in advance.

HTH.


--
Eddy

Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.

These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.