on Sat, Feb 08, 2003 at 07:38:28PM -0800, Adar Dembo ([EMAIL PROTECTED]) wrote: > Hello, > > I'm running Debian Testing on a 2.4.18 box which I use a server. It's > connected to the power and network, no monitor, keyboard, or other > accessories. As a result, the only access I have is through ssh. > > As of late, the box has taken to crashing often. Normally its uptime > was in the dozens of weeks, but now it crashed yesterday, and again > just now. However, nothing in /var/log shows a kernel oops or > anything. What I would like to do is find out why its crashing. Is > there a program I can install to give me more detailed information on > whats going on? Or do I have to attach a monitor/keyboard to see?
The first question is: what's changed? Focus on hardware or kernel configs by priority. Software *can* affect a GNU/Linux system, though it's rare. There's not a heck of a lot you can do to get more information. Hard crashes are, well, hard crashes. The ususal suspects are hardware and kernel modules. There have been buggy drivers that can kill GNU/Linux. 2.4.18 is pretty current, I'm not aware of any showstoppers. Your best bet is to run memory and CPU tests, then start isolating components. Look for any disk errors in your logs (these generally *do* show). You might have a bad card or mobo as well. Try running with drivers not loaded if possible. It would probably also help to monitor memory use (though the OOM should peel you off the ceiling if you're running out of memory), and/or install process accounting so you can see what the last run processes were. Peace. -- Karsten M. Self <[EMAIL PROTECTED]> http://kmself.home.netcom.com/ What Part of "Gestalt" don't you understand? Remember Ed Curry! http://www.iwethey.org/ed_curry/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
