LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
Reload this Page Reboots at 60 minutes
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
Page 2 of 4 1 2 34
  Search this Thread
Old 08-11-2008, 06:30 PM   #16
billymayday
LQ Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122

I'd look at limiting your startup services to see if any of those are causing problems.

I'd start with anacron, at and cron (you can do the fist two from the services settings application under system administration, but I think cron may need to be stopped manually post boot with "sudo /etc/init.d/cron stop". But it may be safer to use this method for everyting you want to stop, since this way, a reboot will reset everything for you.

If they don't help, I'd try acpid and apmd, the system loggers, powernowd.

Outside of that, there are a number of other services in init.d you can stop per session.

Are you sure you don't have any power management setup? What are your screensaver settings?
 
Old 08-11-2008, 10:38 PM   #17
dgermann
Member
 
Registered: Aug 2004
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366

Original Poster
Rep: Reputation: 31
Question
billymayday--

Thanks for helping me.

OK, one thing I tried this evening: I rebooted and let it sit at the grub menu for about 3 hours. Then I ctrl-alt-del and changed the bios clock to Friday 11:45 pm or so. Then I let it boot up, changed the system clock to about the same date and time, and took it off the automatic get the time from the internet thing.

I have been running now for about an hour and a half (the system clock shows Saturday at 1:34 am--actual time is Monday, 11:34 pm), and there have been no auto reboots. I'll let it go overnight and see.

Will report back on what this does....

Here is anacrontab:

Code:
doug@doug2:~$ cat /etc/anacrontab
# /etc/anacrontab: configuration file for anacron

# See anacron(8) and anacrontab(5) for details.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# These replace cron's entries
1	5	cron.daily	 nice run-parts --report /etc/cron.daily
7	10	cron.weekly	 nice run-parts --report /etc/cron.weekly
@monthly	15	cron.monthly nice run-parts --report /etc/cron.monthly

doug@doug2:~$
Not that I know what I'm reading, but I don't think acpid has our clues:
Code:
[Sun Aug 10 00:33:00 2008] logfile reopened
[Sun Aug 10 01:25:55 2008] starting up
[Sun Aug 10 01:25:55 2008] 74 rules loaded
[Sun Aug 10 01:26:01 2008] client connected from 5870[107:116]
[Sun Aug 10 01:26:01 2008] 1 client rule loaded
[Sun Aug 10 01:26:02 2008] client connected from 5987[0:0]
[Sun Aug 10 01:26:02 2008] 1 client rule loaded
[Sun Aug 10 01:26:04 2008] client connected from 5987[0:0]
[Sun Aug 10 01:26:04 2008] 1 client rule loaded
[Sun Aug 10 02:26:11 2008] starting up
[Sun Aug 10 02:26:11 2008] 74 rules loaded
[Sun Aug 10 02:26:17 2008] client connected from 5858[107:116]
[Sun Aug 10 02:26:17 2008] 1 client rule loaded
[Sun Aug 10 02:26:19 2008] client connected from 6001[0:0]
[Sun Aug 10 02:26:19 2008] 1 client rule loaded
[Sun Aug 10 02:26:21 2008] client connected from 6001[0:0]
[Sun Aug 10 02:26:21 2008] 1 client rule loaded
[Sun Aug 10 03:26:29 2008] starting up
[Sun Aug 10 03:26:29 2008] 74 rules loaded
[Sun Aug 10 03:26:35 2008] client connected from 5867[107:116]
[Sun Aug 10 03:26:35 2008] 1 client rule loaded
[Sun Aug 10 03:26:37 2008] client connected from 6010[0:0]
[Sun Aug 10 03:26:37 2008] 1 client rule loaded
[Sun Aug 10 03:26:38 2008] client connected from 6010[0:0]
[Sun Aug 10 03:26:38 2008] 1 client rule loaded
[Sun Aug 10 04:26:47 2008] starting up
[Sun Aug 10 04:26:47 2008] 74 rules loaded
To me this just seems to be reporting that the computer restarted and so did this daemon, on several occasions in the problem time. But it does not seem to say why.

No I am not sure I have no power management set up. If I go to System > Preferences > Power Management, I have three tabs: Under General what shows is Ask me on power button pressed; suspend when suspend button pressed; Never display an icon; Use sound to notify of error.

Under UPS Power I have put computer to sleep never; UPS power low do nothing; ups power critically low shutdown; put display to sleep when 23 minutes inactive.

Under AC Power: put computer to sleep never; put display to sleep when inactive 40 minutes.

That's everything under power management I see--nothing there sounds suspect to me.

APCUPSD Monitor reports these events over this time period:
Code:
Mon Aug 11 18:39:31 EDT 2008  apcupsd shutdown succeeded
Mon Aug 11 18:39:31 EDT 2008  apcupsd exiting, signal 15
Sun Aug 10 09:13:50 EDT 2008  apcupsd shutdown succeeded
Sun Aug 10 09:13:50 EDT 2008  apcupsd exiting, signal 15
Sat Aug 09 18:08:49 EDT 2008  apcupsd shutdown succeeded
Sat Aug 09 18:08:49 EDT 2008  apcupsd exiting, signal 15
Sat Aug 09 12:19:51 EDT 2008  apcupsd shutdown succeeded
Sat Aug 09 12:19:51 EDT 2008  apcupsd exiting, signal 15
Thu Aug 07 20:51:15 EDT 2008  Power is back. UPS running on mains.
Again, it does not even show all the reboots, so power seems to be clean, at least during this period. (The shutdowns I think correspond to when I manually rebooted.)

doug@doug2:~$ apm
No APM support in kernel

So I suspect no apmd is installed--but I do have man files for apmd and apm, suggesting they are installed. Ahh--synaptic shows apmd is installed.

In short, I don't know what you mean by "If they don't help, I'd try acpid and apmd, the system loggers, powernowd."

If this resetting of the clock produces no ill effects, I will then try your method of shutting down cron, and so forth. But I should probably test only one thing at a time, yes?

Is it possible this is hardware?
 
Old 08-11-2008, 11:16 PM   #18
billymayday
LQ Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
I missed the Saturday connection earlier. Suggests very strongly to me something in cron.weekly or, perhaps more likely, a gnome process. I wouldn't think hardware, but who knows.

If you can get it to reboot with you clock deception, try booting to the command line (ie kill gnome) and see if it reboots then. See http://www.linuxquestions.org/questi...d-of-x-549292/ for example
 
Old 08-12-2008, 10:32 AM   #19
dgermann
Member
 
Registered: Aug 2004
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366

Original Poster
Rep: Reputation: 31
Question
billymayday--

A report: this morning all seemed well. There were no reboots. So I reset the system clock in Gnome and then rebooted and reset the clock in bios.

In other words, the experiment gave inconclusive results. (Remember, last time I had this problem was about 4 months ago, and then a week ago.)

What is in cron.weekly is shown in post 13 in this thread. Shall I post the contents of any of these as being a likely culprit? Or perhaps simply move them someplace else one by one?

I think I did run top when all this was going on to see what might have been triggering the reboot, and I saw nothing. But my recollection might not be accurate, either. Something for next time this all happens.

What should I investigate next? Anything particular in gnome? (I did have a problem last week with losing my evolution addressbook, and had to rename the directory ~.gconf/apps/evolution/addressbook. Does that suggest any clues? That was almost a week before the auto reboots started.)

Another piece of info: this problem existed on this machine when I had Ubuntu 7.10 on it, and now after the upgrade to 8.04.01.

Thanks, billymayday!
 
Old 09-09-2008, 06:56 PM   #20
dgermann
Member
 
Registered: Aug 2004
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366

Original Poster
Rep: Reputation: 31
Smile
Hi all--

Just a brief update. The machine continues to run well, so there is no telling what really was wrong. At least I learned a bunch of things to check if and when it happens again!

On a side note: a WinXP box in the office started shutting down (not rebooting) unexpectedly about 2 or 3 weeks ago, and that continued for a couple of days. It did not do it every hour, just once or twice a day for 4 or 5 days in a row.

Strange.

Thanks to everyone for all your help!
 
Old 10-02-2008, 07:48 PM   #21
dgermann
Member
 
Registered: Aug 2004
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366

Original Poster
Rep: Reputation: 31
Question
It was baaaaaaack!

Yesterday into today the problem returned, as this output shows:
Code:
doug@doug2:~$ last
doug     pts/0        :0.0             Thu Oct  2 20:31   still logged in   
doug     pts/0        :0.0             Thu Oct  2 12:19 - 20:23  (08:03)    
doug     pts/0        :0.0             Thu Oct  2 11:53 - 11:54  (00:01)    
doug     tty7         :0               Thu Oct  2 10:31   still logged in   
reboot   system boot  2.6.24-19-generi Thu Oct  2 10:29 - 20:31  (10:02)    
doug     pts/0        :0.0             Thu Oct  2 10:27 - 10:27  (00:00)    
doug     tty7         :0               Thu Oct  2 10:27 - 10:27  (00:00)    
doug     pts/0        :0.0             Thu Oct  2 10:26 - 10:26  (00:00)    
doug     pts/0        :0.0             Thu Oct  2 10:23 - 10:26  (00:02)    
doug     pts/0        :0.0             Thu Oct  2 10:20 - 10:22  (00:01)    
doug     tty7         :0               Thu Oct  2 10:20 - 10:27  (00:06)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 10:19 - 10:27  (00:08)    
doug     tty7         :0               Thu Oct  2 10:16 - crash  (00:03)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 09:19 - 10:27  (01:08)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 08:18 - 10:27  (02:09)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 07:18 - 10:27  (03:09)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 06:18 - 10:27  (04:09)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 05:17 - 10:27  (05:10)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 04:17 - 10:27  (06:10)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 03:17 - 10:27  (07:10)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 02:17 - 10:27  (08:10)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 01:16 - 10:27  (09:11)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 00:16 - 10:27  (10:11)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 23:16 - 10:27  (11:11)    
doug     pts/0        :0.0             Wed Oct  1 23:00 - 23:01  (00:00)    
doug     tty7         :0               Wed Oct  1 22:16 - crash  (00:59)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 22:15 - 10:27  (12:12)    
doug     tty7         :0               Wed Oct  1 21:16 - crash  (00:59)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 21:15 - 10:27  (13:12)    
doug     tty7         :0               Wed Oct  1 20:16 - crash  (00:59)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 20:15 - 10:27  (14:12)    
doug     pts/0        :0.0             Wed Oct  1 19:55 - 19:55  (00:00)    
doug     tty7         :0               Wed Oct  1 19:53 - crash  (00:21)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 19:25 - 10:27  (15:02)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 18:14 - 10:27  (16:13)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 17:14 - 10:27  (17:13)    
doug     tty7         :0               Wed Oct  1 16:21 - crash  (00:53)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 16:14 - 10:27  (18:13)    
doug     pts/0        :0.0             Wed Oct  1 15:35 - 15:37  (00:02)    
doug     tty7         :0               Wed Oct  1 15:35 - crash  (00:38)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 15:13 - 10:27  (19:14)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 14:13 - 10:27  (20:14)    
doug     pts/0        :0.0             Wed Oct  1 13:17 - 13:17  (00:00)    
doug     tty7         :0               Wed Oct  1 13:13 - crash  (00:59)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 13:13 - 10:27  (21:14)    
doug     tty7         :0               Wed Oct  1 12:44 - 12:48  (00:03)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 12:44 - 12:48  (00:04)    
doug     pts/0        :0.0             Wed Oct  1 11:45 - 11:46  (00:00)    
doug     tty7         :0               Wed Oct  1 11:43 - crash  (01:01)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 11:41 - 12:48  (01:07)    
doug     tty7         :0               Wed Oct  1 10:41 - crash  (00:59)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 10:40 - 12:48  (02:07)    
doug     pts/0        :0.0             Wed Oct  1 10:33 - 10:34  (00:00)    
doug     tty7         :0               Wed Oct  1 10:33 - 10:37  (00:04)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 10:32 - 10:37  (00:05)    
doug     pts/0        :0.0             Wed Oct  1 10:29 - 10:30  (00:00)    
doug     pts/0        :0.0             Wed Oct  1 10:25 - 10:29  (00:03)    
doug     tty7         :0               Wed Oct  1 10:24 - crash  (00:07)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 09:32 - 10:37  (01:05)    

wtmp begins Wed Oct  1 09:32:27 2008
doug@doug2:~$
What I think I learned from this:

1. It is not exactly every 60 minutes, but about 60 1/3 minutes--note the progression every few hours.

2. After about a day, it goes away on its own--if I can put up with it.

3. The entry at 13:13 was when I rebooted the machine--notice that the next several automatic reboots were at 13 after the hour. This suggests to me it is not a power problem, nor an UPS problem, but something with the computer itself, and probably the software, since it responded to something I did.

The last time this happened was August 9, so there does not seem to be anything with the dates here--August 9 then October 1.

I post this more to keep a log of it than to ask help. Since the problem seems to have resolved itself (again) after a day, trouble-shooting would be a hit or miss thing.

But is this a clue? It was started at the same time as the last reboot.
Code:
doug@doug2:~$ ls -alt /var/log/gdm
total 48
-rw-r--r--  1 root root 4407 2008-10-02 19:37 :0.log
drwxr-xr-x  2 root root 4096 2008-10-02 10:29 .
drwxr-xr-x 15 root root 4096 2008-10-02 10:29 ..
-rw-r--r--  1 root root 4242 2008-10-02 10:27 :0.log.1
-rw-r--r--  1 root root 4242 2008-10-02 10:20 :0.log.2
-rw-r--r--  1 root root 4242 2008-10-02 10:16 :0.log.3
-rw-r--r--  1 root root 2045 2008-10-02 08:19 :0.log.4
-rw-r--r--  1 root root  128 2008-08-02 17:17 failsafe.log
doug@doug2:~$
FWIW.

Thanks, folks!
 
Old 11-02-2008, 05:10 PM   #22
dgermann
Member
 
Registered: Aug 2004
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366

Original Poster
Rep: Reputation: 31
Question Again in November
Hi--

Just another report, and this is a good place to keep a record of what is going on. I note the last time was the first of the month or thereabouts, too:

Code:
doug@doug2:~$ last reboot
reboot   system boot  2.6.24-19-generi Sun Nov  2 17:24 - 18:05  (00:41)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 16:23 - 18:05  (01:41)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 15:23 - 18:05  (02:41)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 14:23 - 18:05  (03:41)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 13:23 - 18:05  (04:42)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 12:25 - 18:05  (05:39)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 11:22 - 18:05  (06:42)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 10:22 - 18:05  (07:43)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 09:21 - 18:05  (08:43)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 08:21 - 18:05  (09:43)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 07:21 - 18:05  (10:44)    

wtmp begins Sun Nov  2 07:21:20 2008
doug@doug2:~$
This time a weekend, last time mid week.

We shall see what we shall see.
 
Old 11-02-2008, 05:16 PM   #23
billymayday
LQ Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
DO you have anything in /var/spool/cron or similar directory (this should be where user crontabs are kept)?

If so, post

# cat /var/spool/cron/*

or at least look for monthly jobs.

What's in /etc/cron.monthly?
Last edited by billymayday; 11-02-2008 at 05:18 PM.
 
Old 11-02-2008, 05:33 PM   #24
dgermann
Member
 
Registered: Aug 2004
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366

Original Poster
Rep: Reputation: 31
Question
billymayday--

Thanks for continuing to watch this and jumping in to help. This is a really puzzler, huh?

Code:
doug@doug2:~$ cat /var/spool/cron/*
cat: /var/spool/cron/atjobs: Permission denied
cat: /var/spool/cron/atspool: Permission denied
cat: /var/spool/cron/crontabs: Permission denied
doug@doug2:~$ sudo ls -alh /var/spool/cron/atjobs
[sudo] password for doug: 
total 12K
drwxrwx--T 2 daemon daemon 4.0K 2007-12-05 21:42 .
drwxr-xr-x 5 daemon daemon 4.0K 2007-12-05 21:40 ..
-rw------- 1 daemon daemon    2 2007-12-05 21:42 .SEQ
doug@doug2:~$ sudo less /var/spool/cron/atjobs/.SEQ
doug@doug2:~$ sudo cat /var/spool/cron/atjobs/.SEQ
0
doug@doug2:~$ sudo ls -alh /var/spool/cron/atspool/
total 8.0K
drwxrwx--T 2 daemon daemon 4.0K 2007-02-20 08:41 .
drwxr-xr-x 5 daemon daemon 4.0K 2007-12-05 21:40 ..
doug@doug2:~$ sudo ls -alh /var/spool/cron/crontabs/
total 16K
drwx-wx--T 2 root   crontab 4.0K 2008-10-22 18:27 .
drwxr-xr-x 5 daemon daemon  4.0K 2007-12-05 21:40 ..
-rw------- 1 doug   crontab  230 2008-10-22 18:20 doug
-rw------- 1 root   crontab 1.4K 2008-10-22 18:27 root
doug@doug2:~$ sudo cat /var/spool/cron/crontabs/doug
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.PdhP42/crontab installed on Wed Oct 22 18:20:22 2008)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
# m h  dom mon dow   command
doug@doug2:~$ sudo cat /var/spool/cron/crontabs/root
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.Brwdy5/crontab installed on Wed Oct 22 18:27:55 2008)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
# m h dom mon dow
7 0 * * * /etc/webmin/cron/tempdelete.pl
# * * * * * touch /sam/vol22/data/todo/bak/2crontest

####copied from sdb1 (old drive) and refers there 20071208: did not
 work so commented out for now; changed to new locations 20071210:

0 * * * * /usr/sbin/esets_update
# * * * * * root /usr/bin/touch /sam/vol22/data/todo/bak/1crontest

##############ddg 20061113 updated for new directories 20071210:

#0 3 * * * /usr/sbin/esets_scan -l --mail –unsafe / -- -/dev* 
-/proc* -/sam* -/media/sdb1/dev* -/media/sdb1/proc* 
-/media/sdb1/sam*


###20080715 ddg:
#0 3 * * * /usr/sbin/esets_scan -f /var/log/esets/scan.log / 
--exclude /dev /proc /sam
0 3 * * * /etc/cron.doug/eset
#0 21 * * * /etc/cron.doug/eset
###
#30 * * * *         cp -pru ~doug/.evolution /sam/vol22/comm/evo/
30 * * * *         rsync -a --delete ~doug/.evolution/ /sam/vol22/comm/evo

#######added by ddg 20080115:
21 15 * * *     root     cp -u /sam/vol22/data/ts/TSBACKUP.BKU ~doug

#######end of addition 20080115

###added by ddg 20080120:
31 01 18 1,3,5,7,9,11 * /etc/cron.doug/bkmonthone
31 01 18 2,4,6,8,10,12 * /etc/cron.doug/bkmonthtwo
# 31 01 18 3,6,9,12 * /etc/cron.doug/bkmonththree
###





doug@doug2:~$
So: there is nothing here for the first or second day of the month, nor for the 23rd minute, at least as far as I am seeing. Perhaps you see another clue?

Thanks, billymayday!
Last edited by dgermann; 11-02-2008 at 05:35 PM. Reason: shorten lines
 
Old 11-02-2008, 05:52 PM   #25
billymayday
LQ Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
One of the problems is wtmp doesn't go back that far. Clearly the first (?) reboot was at 7:21, and it's rebooted every hour is my guess, which has pushed the minutes out to 23 not 21. I guess it's possible that it started rebooting earlier but the log was rotated around this time.

Can you look in /var/log and see if you have wtmp.1 or similar (I'm assuming here that /var/log/wtmp exists and is the relevant log). If it does, try

last -f /var/log/wtmp.1 reboot

or similar for relevant file to try and determine the first reboot of the cycle. If you've found the first at 7:21, I'd be thinking log rotations perhaps.

What's in /etc/cron.monthly?
 
Old 11-02-2008, 06:16 PM   #26
dgermann
Member
 
Registered: Aug 2004
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366

Original Poster
Rep: Reputation: 31
Question
billymayday--

The first one was the day before at 16:22, so perhaps you are on to something with logrotate:

Code:
doug@doug2:~$ sudo last -f /var/log/wtmp.1 reboot
[sudo] password for doug: 
reboot   system boot  2.6.24-19-generi Sat Nov  1 16:22 - 19:14 (1+03:51)   
reboot   system boot  2.6.24-19-generi Thu Oct  2 10:29 - 14:44 (27+04:14)  
reboot   system boot  2.6.24-19-generi Thu Oct  2 10:19 - 10:27  (00:08)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 09:19 - 10:27  (01:08)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 08:18 - 10:27  (02:09)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 07:18 - 10:27  (03:09)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 06:18 - 10:27  (04:09)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 05:17 - 10:27  (05:10)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 04:17 - 10:27  (06:10)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 03:17 - 10:27  (07:10)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 02:17 - 10:27  (08:10)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 01:16 - 10:27  (09:11)    
reboot   system boot  2.6.24-19-generi Thu Oct  2 00:16 - 10:27  (10:11)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 23:16 - 10:27  (11:11)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 22:15 - 10:27  (12:12)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 21:15 - 10:27  (13:12)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 20:15 - 10:27  (14:12)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 19:25 - 10:27  (15:02)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 18:14 - 10:27  (16:13)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 17:14 - 10:27  (17:13)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 16:14 - 10:27  (18:13)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 15:13 - 10:27  (19:14)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 14:13 - 10:27  (20:14)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 13:13 - 10:27  (21:14)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 12:44 - 12:48  (00:04)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 11:41 - 12:48  (01:07)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 10:40 - 12:48  (02:07)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 10:32 - 10:37  (00:05)    
reboot   system boot  2.6.24-19-generi Wed Oct  1 09:32 - 10:37  (01:05)    

wtmp.1 begins Wed Oct  1 09:32:27 2008
doug@doug2:~$
Code:
doug@doug2:~$ ls -alh /etc/cron.monthly/
total 32K
drwxr-xr-x   2 root root 4.0K 2008-09-07 21:37 .
drwxr-xr-x 149 root root  12K 2008-11-02 18:24 ..
-rwxr-xr-x   1 root root  313 2007-03-05 01:38 0anacron
-rw-r--r--   1 root root  102 2006-12-20 09:46 .placeholder
-rwxr-xr-x   1 root root  106 2007-12-06 08:21 scrollkeeper
-rwxr-xr-x   1 root root  129 2006-12-20 09:46 standard
doug@doug2:~$ less /etc/cron.monthly/0anacron 
doug@doug2:~$ cat /etc/cron.monthly/0anacron 
#!/bin/sh
#
# anacron's cron script
#
# This script updates anacron time stamps. It is called through run-parts
# either by anacron itself or by cron.
#
# The script is called "0anacron" to assure that it will be executed
# _before_ all other scripts.

test -x /usr/sbin/anacron || exit 0
anacron -u cron.monthly
doug@doug2:~$ cat /etc/cron.monthly/.placeholder 
# DO NOT EDIT OR REMOVE
# This file is a simple placeholder to keep dpkg from removing this directory
doug@doug2:~$ cat /etc/cron.monthly/scrollkeeper
#!/bin/sh

set -e

[ -x /usr/bin/scrollkeeper-rebuilddb ] || exit 0

umask 022
scrollkeeper-rebuilddb -q

doug@doug2:~$ cat /etc/cron.monthly/standard 
#!/bin/sh
# /etc/cron.monthly/standard: standard monthly maintenance script

# rotation of wtmp and btmp taken over by logrotate
doug@doug2:~$
Thanks, billymayday!
Last edited by dgermann; 11-02-2008 at 06:20 PM.
 
Old 11-03-2008, 07:56 PM   #27
dgermann
Member
 
Registered: Aug 2004
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366

Original Poster
Rep: Reputation: 31
Question Clues, clues?
Hi--

It has continued today a second day--in the past it has stopped after a day or so. If my memory is accurate.

Here's what happens, in case it is a clue: I will be sitting typing away and then I hear the computer fan start up. I can save a document--I appear to have about 3 to 5 seconds, and then it goes into a reboot.

Here is the latest string of reboots:
Code:
doug@doug2:~$ last reboot
reboot   system boot  2.6.24-19-generi Mon Nov  3 20:41 - 20:48  (00:06)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 20:22 - 20:39  (00:16)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 19:22 - 20:39  (01:16)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 18:25 - 20:39  (02:13)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 17:21 - 17:47  (00:25)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 16:21 - 17:47  (01:25)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 15:21 - 17:47  (02:25)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 14:20 - 17:47  (03:26)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 13:20 - 17:47  (04:26)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 12:20 - 17:47  (05:26)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 11:20 - 17:47  (06:27)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 10:15 - 17:47  (07:31)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 09:15 - 17:47  (08:31)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 08:28 - 09:13  (00:44)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 07:28 - 09:13  (01:44)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 06:28 - 09:13  (02:45)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 05:27 - 09:13  (03:45)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 04:27 - 09:13  (04:45)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 03:27 - 09:13  (05:45)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 02:26 - 09:13  (06:46)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 01:26 - 09:13  (07:46)    
reboot   system boot  2.6.24-19-generi Mon Nov  3 00:26 - 09:13  (08:46)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 23:26 - 09:13  (09:47)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 22:25 - 09:13  (10:47)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 21:25 - 09:13  (11:47)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 20:25 - 09:13  (12:48)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 19:35 - 09:13  (13:37)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 18:24 - 09:13  (14:48)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 17:24 - 09:13  (15:48)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 16:23 - 09:13  (16:49)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 15:23 - 09:13  (17:49)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 14:23 - 09:13  (18:49)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 13:23 - 09:13  (19:50)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 12:25 - 09:13  (20:47)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 11:22 - 09:13  (21:50)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 10:22 - 09:13  (22:51)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 09:21 - 09:13  (23:51)    
reboot   system boot  2.6.24-19-generi Sun Nov  2 08:21 - 09:13 (1+00:51)   
reboot   system boot  2.6.24-19-generi Sun Nov  2 07:21 - 09:13 (1+01:51)   

wtmp begins Sun Nov  2 07:21:20 2008
doug@doug2:~$
See anything that is a clue?

Thanks!
 
Old 11-03-2008, 08:51 PM   #28
dgermann
Member
 
Registered: Aug 2004
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366

Original Poster
Rep: Reputation: 31
Clues?
Hi--

Is this a clue? I'm not sure what it is saying:
Code:
doug@doug2:~$ less /var/log/cron.log |grep boot
Nov  1 16:21:19 doug2 /usr/sbin/cron[6274]: (CRON) INFO (Running @reboot jobs)
Nov  2 07:21:32 doug2 /usr/sbin/cron[6267]: (CRON) INFO (Running @reboot jobs)
Nov  2 08:21:47 doug2 /usr/sbin/cron[6486]: (CRON) INFO (Running @reboot jobs)
Nov  2 09:22:06 doug2 /usr/sbin/cron[6248]: (CRON) INFO (Running @reboot jobs)
Nov  2 10:22:24 doug2 /usr/sbin/cron[6259]: (CRON) INFO (Running @reboot jobs)
Nov  2 11:22:41 doug2 /usr/sbin/cron[6250]: (CRON) INFO (Running @reboot jobs)
Nov  2 12:26:08 doug2 /usr/sbin/cron[8544]: (CRON) INFO (Running @reboot jobs)
Nov  2 13:23:16 doug2 /usr/sbin/cron[6244]: (CRON) INFO (Running @reboot jobs)
Nov  2 14:23:34 doug2 /usr/sbin/cron[6255]: (CRON) INFO (Running @reboot jobs)
Nov  2 15:23:52 doug2 /usr/sbin/cron[6234]: (CRON) INFO (Running @reboot jobs)
Nov  2 16:24:11 doug2 /usr/sbin/cron[6254]: (CRON) INFO (Running @reboot jobs)
Nov  2 17:24:26 doug2 /usr/sbin/cron[6480]: (CRON) INFO (Running @reboot jobs)
Nov  2 18:24:40 doug2 /usr/sbin/cron[6492]: (CRON) INFO (Running @reboot jobs)
Nov  2 19:36:00 doug2 /usr/sbin/cron[14545]: (CRON) INFO (Running @reboot jobs)
Nov  2 20:25:22 doug2 /usr/sbin/cron[6264]: (CRON) INFO (Running @reboot jobs)
Nov  2 21:25:41 doug2 /usr/sbin/cron[6269]: (CRON) INFO (Running @reboot jobs)
Nov  2 22:25:56 doug2 /usr/sbin/cron[6252]: (CRON) INFO (Running @reboot jobs)
Nov  2 23:26:13 doug2 /usr/sbin/cron[6250]: (CRON) INFO (Running @reboot jobs)
Nov  3 00:26:31 doug2 /usr/sbin/cron[6243]: (CRON) INFO (Running @reboot jobs)
Nov  3 01:26:50 doug2 /usr/sbin/cron[6250]: (CRON) INFO (Running @reboot jobs)
Nov  3 02:27:08 doug2 /usr/sbin/cron[6247]: (CRON) INFO (Running @reboot jobs)
Nov  3 03:27:29 doug2 /usr/sbin/cron[6259]: (CRON) INFO (Running @reboot jobs)
Nov  3 04:27:43 doug2 /usr/sbin/cron[6253]: (CRON) INFO (Running @reboot jobs)
Nov  3 05:28:00 doug2 /usr/sbin/cron[6237]: (CRON) INFO (Running @reboot jobs)
Nov  3 06:28:19 doug2 /usr/sbin/cron[6253]: (CRON) INFO (Running @reboot jobs)
Nov  3 07:28:37 doug2 /usr/sbin/cron[6244]: (CRON) INFO (Running @reboot jobs)
Nov  3 08:28:53 doug2 /usr/sbin/cron[6250]: (CRON) INFO (Running @reboot jobs)
Nov  3 09:15:27 doug2 /usr/sbin/cron[6262]: (CRON) INFO (Running @reboot jobs)
Nov  3 10:15:51 doug2 /usr/sbin/cron[6500]: (CRON) INFO (Running @reboot jobs)
Nov  3 11:20:12 doug2 /usr/sbin/cron[6503]: (CRON) INFO (Running @reboot jobs)
Nov  3 12:20:35 doug2 /usr/sbin/cron[6258]: (CRON) INFO (Running @reboot jobs)
Nov  3 13:20:54 doug2 /usr/sbin/cron[6268]: (CRON) INFO (Running @reboot jobs)
Nov  3 14:21:02 doug2 /usr/sbin/cron[6259]: (CRON) INFO (Running @reboot jobs)
Nov  3 15:21:31 doug2 /usr/sbin/cron[6265]: (CRON) INFO (Running @reboot jobs)
Nov  3 16:21:45 doug2 /usr/sbin/cron[6266]: (CRON) INFO (Running @reboot jobs)
Nov  3 17:21:55 doug2 /usr/sbin/cron[6263]: (CRON) INFO (Running @reboot jobs)
Nov  3 18:25:32 doug2 /usr/sbin/cron[8589]: (CRON) INFO (Running @reboot jobs)
Nov  3 19:22:39 doug2 /usr/sbin/cron[6474]: (CRON) INFO (Running @reboot jobs)
Nov  3 20:22:56 doug2 /usr/sbin/cron[6247]: (CRON) INFO (Running @reboot jobs)
Nov  3 20:41:33 doug2 /usr/sbin/cron[6249]: (CRON) INFO (Running @reboot jobs)
doug@doug2:~$
Also, I have a second hard drive, SDB1, which used to have my boot files on it--a full /etc for instance. Is it possible that something there is activating? This problem first appeared after I got the new drive....
 
Old 11-04-2008, 12:18 AM   #29
billymayday
LQ Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
No, but since you've got a pretty good idea when it will happen next, try capturing all the processes that are running after the fan fires up (ps aux > ps.file) or something. Or better yet, a minute or so before you expect it to go down, run a script that writes that output to a file every second or so - something like

Code:
#!/bin/sh
#

while [ 1 ];
do
        echo $(date) >> ps.file
        ps aux >> ps.file
        echo >> ps.file
        echo >> ps.file
        sleep 2
done
 
Old 11-05-2008, 09:50 PM   #30
dgermann
Member
 
Registered: Aug 2004
Distribution: Ubuntu 16.04 lts desk; Ubuntu 14.04 server
Posts: 366

Original Poster
Rep: Reputation: 31
Question
billymayday--

That's worth a shot! Will let you know what happens.

Thanks, billymayday!
 
  


Reply
Page 2 of 4 1 2 34

Tags
automatic, rebooting



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
PC Reboots over and over lmanwarren Linux - Hardware 1 04-16-2005 08:26 PM
2.6.10 reboots salted Slackware 6 02-12-2005 09:30 PM
server reboots every 52 minutes cazzazullu Linux - Hardware 2 10-18-2004 06:34 AM
computer reboots ~5 minutes after halting lpc911 Linux - General 0 06-27-2004 03:30 AM
reboots itself ace135cc Slackware 3 09-13-2003 09:48 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 03:37 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration