Reboot every 1 hour, 19 seconds

Todd Denniston Todd.Denniston at ssa.crane.navy.mil
Tue Oct 7 15:22:24 UTC 2008


Rodolfo Alcazar Portillo wrote, On 10/07/2008 11:00 AM:
> Am Dienstag, den 07.10.2008, 09:48 -0500 schrieb Arthur Pemberton:
>> When was the last time you dismantled and cleaned the machine?
> 
> Arthur:
> 
> Three monts ago? Seems clean, though. 
> - I changed the memory DIMMs. 

Before or after the rebooting started?

> - Disconnected the machine electrig plug. 
> - Pushed RESET button for about a minute. 
> 
> I repeat: since the power outage, it reboots every 1.00.19, approx.
> 

tried coming up in single user mode and running something like:
e2fsck -y -c -k -v -C 0 /dev/rootdevice

yes, normally ext3 does not have problems with power drops and such, but it 
can over time build up some things that need cleaned up, and at a minimum a 
read-only media check can be a good thing {read-write is better, but takes a 
looooong time}.

> Tim: 
> 
> could not be a cron issue, that would lead to exactly 1 hour rebooting.
> Every 3 reboots means 3 hours and a minute (look my previous logs).

How long does it to reboot? ~19 seconds?
How long does it take for the program that is getting started at 1 hour after 
the machine comes up, to use enough power|memory to cause a fault? ~19 seconds?

BTW been here and bought the tee shirt... My machine had a problem of using a 
little more current than the wires supplying it could carry, while trying to 
get cron.daily done and doing it's other work.

suggestion: bring the box up in runlevel 3 and come back to it about 58 
minutes after you boot it, you might actually see the kernel give an OOPS or 
panic. [If you don't have the patience to do that, there is the option of 
setting up a serial console to another machine and logging the console there.]
reason for runlevel 3: so you see console messages instead of GDM.

> 
> # ls -l /etc/cron.hourly/
> total 0

Means little, as if the machine has not been able to complete .daily or 
.weekly or .monthly in that time period, then it will start running those at 
~1 hour after boot.

try:
  ls -ltr /var/spool/anacron/


> # at -l
> # uname -r
> 2.6.26.5-45.fc9.i686

-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter




More information about the fedora-list mailing list