Here's what I'd do. Download Servers Alive, it's semi-free and it lets you monitor your servers easily. Have Servers alive ping the box every minuite, and send you an email when it goes down. Continue to try to resolve the problem. Monitor the time it crashes. If it's crashing at the same time every nite, I'd point to a cron job. If it's a cron job, maybe look through cron, and spread the times around a bit, so you can determine which job it is. Or redirect all cron output to a file so you can see where it stops. You could actually do this anyway, and it might help. Or just "ps aux >> /appropriate/place/mylog ; date >> /appropriate/place/mylog" into a continually growing file. set it as a cronjob that runs every minuite. It'll get big pretty fast, so use it somewhere that has lots of room, and delete it before you leave at night, and in the AM. If you want to get fancy, create a small script.
rm -rf /appropriate/place/mylog.old mv /appropriate/place/mylog /appropriate/place/mylog.old ps aux >> /appropriate/place/mylog date >> /appropriate/place/mylog That would save you from worrying about disk space. Then I'd go in a bit early tomorrow, and write out the full text of the message so you could post it here in more detail. PID 0 seems strange to me. I thought PIDs started at 1 which will always be init. Kev. ----- Original Message ----- From: "Evan Brown" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 05, 2003 7:50 AM Subject: (clug-talk) kernal panic > So it froze again last night, could it be some cron job running and > messing stuff up? The error said something about interput not syncing and > pid was 0 and a bunch of hex values and then nothing. What the hell? It > seems to crash every night. I come in at 7:30am and its crashed during the > night, this is the 4th time its happened. > > Evan Brown > > >
