Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
It won't help diagnose this crash, but if it's feasible, I would setup your box with serial console support, and a second machine with a serial connection to your crashed server to capture console output. Depending on the budget, this can be a low-end intel, or one of the commercial remote console solutions. In any case, there's a better-than-average chance that any messages associated with a crash appear on the console and would be captured in a log file on the 2nd box. Just 2 cents Gordon Keegan --- FRamsay at castelhq.com wrote: > Does anyone know of any tools to help figure out why > a box rebooted? One > of our client boxes rebooted > over the weekend for no apparent reason. The client > claimed there was no > power outage, and a quick look > over the logs verifies the UPS didn't shut the > computer down. Also I > didn't see a shutdown or reboot request > in /var/log/messages. So what tools do people use > to figure out why a > Linux system crashed? > > the system is running Redhat 7.2 kernel 2.4.9-13 > > -fjr > > > Frank Ramsay > Systems Programmer > Castel, Inc > 14 Summer St, 3rd Floor > Malden, MA 02148 > (781) 324-0140 (voice) > (781) 324-0277 (fax) > Emal: framsay at castel.com > > > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://www.blu.org/mailman/listinfo/discuss __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |