Re: Server rebooted at 3 a.m. and 7 a.m. for the past few days

On Friday 15 August 2003 02:16, Magnus J wrote: Hello Running /usr/local/etc/cvsup/update.sh manually caused the machine to reboot. Unfortunately, /var/log/cvsup.log doesn't provide any information about why. Any recommendation on what I should use to get more messages? Have you tried

RE: Server rebooted at 3 a.m. and 7 a.m. for the past few days

Hello I tried to start up my Distributed Folding client, which consumes quite a lot of CPU, and it didn't take long before the machine rebooted. I guess the CPU fan is the first thing I will look at when I get back home. This is a PIII 850 MHz Slot 1. I've never had any problems with them

Server rebooted at 3 a.m. and 7 a.m. for the past few days

Hello everyone I'm not sure if I should have posted this to freebsd-security, but I start here. I'm out traveling, and finally got a chance to login to my server back home through SSH, which is running 4.8 and is protected by an IPFILTER firewall. Looking at /var/log/messages , the server has

Re: Server rebooted at 3 a.m. and 7 a.m. for the past few days

Hello Thanks for replying. /etc/crontab looks OK. This is how 'last' looks like (user1 is myself) user1 ttyp0zzz.12.28.40 Thu Aug 14 12:43 - 13:30 (00:46) user1 ttyp1zzz.12.28.40 Thu Aug 14 12:20 - 13:30 (01:09) user1 ttyp0zzz.12.28.40

RE: Server rebooted at 3 a.m. and 7 a.m. for the past few days

Do you have any scripts that run at those times? If you run something like a database update or something that can crank some CPU cycles, you could be overheating the box, causing a reboot. Could happen all of a sudden if a fan decided to quit... Dmesg show any panics? -Original

Re: Server rebooted at 3 a.m. and 7 a.m. for the past few days

Hello sockstat -4 didn't show anything unusual: sshd, cvsupd, java, portmap and ntpd. It seems as if the reboots are happening during the daily periodic and when cvsup runs around 7 a.m. in the morning. I just monitored before the 3 a.m. reboot, and there was no reboot message printed when I

RE: Server rebooted at 3 a.m. and 7 a.m. for the past few days

Hello dmesg shows no panic, and nothing that consumes much CPU has been running since the first reboot. Around 3 a.m. the daily periodic runs (which is default) and around 7 a.m. cvsup runs. Thanks Magnus --- Brent Wiese [EMAIL PROTECTED] skrev: Do you have any scripts that run at those

Re: Server rebooted at 3 a.m. and 7 a.m. for the past few days

- Original Message - (BFrom: "Magnus J" [EMAIL PROTECTED] (BTo: "Brent Wiese" [EMAIL PROTECTED] (BCc: [EMAIL PROTECTED] (BSent: Friday, August 15, 2003 10:44 AM (BSubject: RE: Server rebooted at 3 a.m. and 7 a.m. for the past few days (B (B (B Hello (B (B (B dmesg shows no

Re: Server rebooted at 3 a.m. and 7 a.m. for the past few days

Hello Running /usr/local/etc/cvsup/update.sh manually caused the machine to reboot. Unfortunately, /var/log/cvsup.log doesn't provide any information about why. Any recommendation on what I should use to get more messages? Thanks Magnus --- Luke Kearney [EMAIL PROTECTED] skrev: -

Re: Server rebooted at 3 a.m. and 7 a.m. for the past few days

On Fri, Aug 15, 2003 at 03:44:52AM +0200, Magnus J wrote: Hello dmesg shows no panic, and nothing that consumes much CPU has been running since the first reboot. Around 3 a.m. the daily periodic runs (which is default) and around 7 a.m. cvsup runs. How about taking cron down until you

RE: Server rebooted at 3 a.m. and 7 a.m. for the past few days

There are several system utils that'll stress the CPU/disk in the ports section. I'd try some of those to see if you can cause a reboot. If so, it might help diagnose... If you have a bad cpu fan, it doesn't take much to crash the box. I've seen this a lot in older dual p2/p3 box style cpus. The