Charlie Garrison said: > Any feedback or suggestions would be greatly appreciated. I have been > trying to solve this for about 4 months now, and I don't know what else to > try.
setup a 2nd system, connect a null modem cable between the 2. setup serial console on the system that appears to be crashing. on the 2nd system setup something like minicom to log to a file. load minicom in something like screen to load it in the background and have it log. is the system on a UPS? if so is there software installed to monitor the UPS? is the location of this server secure? that is someone isn't tripping over the power plug, or pulling it out on purpose, or doing something else to it? is the system under heavy load normally? what is the typical load average of the machine(15 minute average). if it's consistantly staying above say 3.00, then I would consider it pretty heavily loaded.(most of my systems are 0.10 or less, some are even 0.04 or less). serial console is the best bet though, if it is crashing such as kernel panic or something you'll get the full kernel dump on the serial port, logged to a file for later enjoyment. I also prefer to log to a syslog server but linux isn't very robust when it comes to crashing and if it crashes it doesn't tend to log to the syslog server(solaris does, at least in the crashes I have experienced). Theres tons of docs out there on how to configure a console serial port. nate -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
