• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Sheevaplug restarts at 6:25  (Read 1332 times)
Manaslu
Newbie
*

Karma: 0
Posts: 13


View Profile
« on: February 22, 2011, 03:17:46 AM »

Every day at 06:25, my Sheevaplug restarts. This is the line from syslog:

Feb 21 06:25:14 Sheeva_1 syslogd 1.5.0#5ubuntu3: restart.

Does anyone have an idea where this comes from? Thanks!
Logged

2 x NSLU2 + Slimserver + rsync. 2 x USB 500GB. Guruplug Standard

Manaslu
Newbie
*

Karma: 0
Posts: 13


View Profile
« Reply #1 on: February 22, 2011, 04:21:55 AM »

OK, found some more, it comes from /etc/cron.daily.

I am now trying to find out which of the files in there causes the restart, but there is an awful number of commands involved and I don't see at the moment which of those has the restart as a (side) effect.
Logged

2 x NSLU2 + Slimserver + rsync. 2 x USB 500GB. Guruplug Standard

birdman
Sr. Member
****

Karma: 4
Posts: 429


View Profile WWW
« Reply #2 on: February 22, 2011, 05:04:07 PM »

Every day at 06:25, my Sheevaplug restarts. This is the line from syslog:

Feb 21 06:25:14 Sheeva_1 syslogd 1.5.0#5ubuntu3: restart.
Isn't that syslogd restarting?  As part of log rotation?
The logs get renamed, then syslgod is sent a HUP to re-open all of its log files.

What makes you think the Plug is restarting.  What does uptime report for the system uptime?
Logged

Manaslu
Newbie
*

Karma: 0
Posts: 13


View Profile
« Reply #3 on: February 23, 2011, 02:18:23 AM »

Every day at 06:25, my Sheevaplug restarts. This is the line from syslog:

Feb 21 06:25:14 Sheeva_1 syslogd 1.5.0#5ubuntu3: restart.
Isn't that syslogd restarting?  As part of log rotation?
The logs get renamed, then syslgod is sent a HUP to re-open all of its log files.

What makes you think the Plug is restarting.  What does uptime report for the system uptime?

Good point, I noticed that the checksum of my two attached USB-disks changes at exactly that moment. That is, cron initiates a comparison of "old" and "new" checksum every hour (hh:00). If the checksums are the same, the disks are spun down. At 06:00 the command is "spin down". At 07:00 the log says "do nothing", meaning the checksums differ.

The conclusion is that "someone" has done "something" on the disks between 06:00 and 07:00. The only thing I find in syslog is this "Feb 21 06:25:14 Sheeva_1 syslogd 1.5.0#5ubuntu3: restart". But cron.daily contains a fair number of scripts that are all executed at 06:25, and perhaps not all of the actions are shown in syslog.

Grateful for any suggestions, I will continue setting up logs and try to find out if really something is happening on the disks. I don't want the disks to spin up every night for no reason.
Logged

2 x NSLU2 + Slimserver + rsync. 2 x USB 500GB. Guruplug Standard

birdman
Sr. Member
****

Karma: 4
Posts: 429


View Profile WWW
« Reply #4 on: February 23, 2011, 02:55:34 PM »

Grateful for any suggestions, I will continue setting up logs and try to find out if really something is happening on the disks. I don't want the disks to spin up every night for no reason.
How are you checksumming the disks every hour without spinning them up?
Why not get the script, if it is 7am, and if it sees a change, to run find to list all entries with "-mmin -60" and mail the result (or leave it in /var/tmp for you to peruse later)?
Logged

Pages: [1]
Print
Jump to: