Kurobox NAS-Central Forums

Welcome to the Kuro Community
It is currently Sun Jun 24, 2018 7:14 am

All times are UTC-06:00




Forum locked  This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
PostPosted: Mon Mar 05, 2007 10:23 am 
Offline

Joined: Fri Feb 02, 2007 11:47 pm
Posts: 6
I installed Debian from scratch a couple of days ago and it took me some time until I got everything working (new Torrentflux and new SABnzbd) and updated everything to the latest version through "Apt".

However I recently observed that every after night my TorrentFlux 2.3 client would stop downloading/seeding torrents and my SABnzbd client is stopped. I checked the /var/log/daemon.log and I found the following:

Code:
Mar  4 22:19:15 SACRED-KURO smartd[4744]: Device: /dev/hda, SMART Usage Attribute: 194 Temperature_Celsius changed from 118 to 119 
Mar  5 00:19:16 SACRED-KURO smartd[4744]: Device: /dev/hda, SMART Usage Attribute: 194 Temperature_Celsius changed from 119 to 120
Mar  5 00:49:15 SACRED-KURO smartd[4744]: Device: /dev/hda, SMART Usage Attribute: 194 Temperature_Celsius changed from 120 to 121
Mar  5 01:15:03 SACRED-KURO init: Switching to runlevel: 0
Mar  5 01:15:12 SACRED-KURO mon[2019]: caught TERM signal, exiting
Mar  5 01:15:15 SACRED-KURO mysqld[1914]: 070305  1:15:15 [Note] /usr/sbin/mysqld: Normal shutdown
Mar  5 01:15:15 SACRED-KURO mysqld[1914]:
Mar  5 01:15:15 SACRED-KURO mysqld[1914]: 070305  1:15:15  InnoDB: Starting shutdown...
Mar  5 01:15:19 SACRED-KURO mysqld[1914]: 070305  1:15:19  InnoDB: Shutdown completed; log sequence number 0 43655
Mar  5 01:15:19 SACRED-KURO mysqld[1914]: 070305  1:15:19 [Note] /usr/sbin/mysqld: Shutdown complete
Mar  5 01:15:19 SACRED-KURO mysqld[1914]:
Mar  5 01:15:19 SACRED-KURO mysqld_safe[5133]: ended
Mar  5 01:15:20 SACRED-KURO ntpd[2086]: ntpd exiting on signal 15
Mar  5 06:19:07 SACRED-KURO mysqld_safe[1914]: started
Mar  5 06:19:08 SACRED-KURO mysqld[1917]: 070305  6:19:08  InnoDB: Started; log sequence number 0 43655
Mar  5 06:19:08 SACRED-KURO mysqld[1917]: 070305  6:19:08 [Note] /usr/sbin/mysqld: ready for connections.
Mar  5 06:19:08 SACRED-KURO mysqld[1917]: Version: '5.0.32-Debian_7-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian etch distribution
Mar  5 06:19:10 SACRED-KURO /etc/mysql/debian-start[1965]: Upgrading MySQL tables if necessary.
Mar  5 06:19:12 SACRED-KURO /etc/mysql/debian-start[1994]: Checking for crashed MySQL tables.
Mar  5 06:19:15 SACRED-KURO ntpdate[1731]: step time server 213.222.193.35 offset 0.700206 sec
Mar  5 06:19:17 SACRED-KURO mon[2022]: running as daemon
Mar  5 06:19:17 SACRED-KURO mon[2022]: mon server started
Mar  5 06:19:20 SACRED-KURO ntpd[2088]: ntpd 4.2.2p4@1.1585-o Sat Oct 21 15:09:34 UTC 2006 (1)
Mar  5 06:19:20 SACRED-KURO ntpd[2089]: precision = 1.000 usec
Mar  5 06:19:20 SACRED-KURO ntpd[2089]: Listening on interface wildcard, 0.0.0.0#123 Disabled
Mar  5 06:19:20 SACRED-KURO ntpd[2089]: Listening on interface lo, 127.0.0.1#123 Enabled
Mar  5 06:19:20 SACRED-KURO ntpd[2089]: Listening on interface eth0, 192.168.1.110#123 Enabled
Mar  5 06:19:20 SACRED-KURO ntpd[2089]: kernel time sync status 0040
Mar  5 06:19:20 SACRED-KURO ntpd[2089]: frequency initialized 8.538 PPM from /var/lib/ntp/ntp.drift
Mar  5 06:19:30 SACRED-KURO ntpd[2089]: synchronized to 81.210.250.102, stratum 2
Mar  5 06:19:30 SACRED-KURO ntpd[2089]: kernel time sync enabled 0001
Mar  5 06:25:45 SACRED-KURO ntpd[2089]: synchronized to 80.190.252.238, stratum 2


It seems that for some reason my system shuts down at 1:15:00 every night and starts right up at 6:19:00. As a results all of my TF/SABnzbd sessions stop.

I also saw the TERM signal at about 1:10:00 while working on the console about 2 days ago warining me that the system will shutdown in 5 minutes.

What could in be causing the Shutdown to occurr. I do not see any scheduled processes that might force this to happen, unless I am checking at the wrong spot.

I am running Debian with lighttp, MYSQL + PHP5, TF 2.3 and latest SABnzbd. In addition I installed avr_evtd after removing kuroevtd.

Any ideas?

Thanks..........


Top
   
 Post subject:
PostPosted: Mon Mar 05, 2007 11:58 am 
Offline

Joined: Fri Feb 02, 2007 11:47 pm
Posts: 6
I think I found the problem.

The kuroevtd Daemon was instructing the AVR Watchdog to shutdown and restart at these times.

I had left the Default values.

Thanks!!!!!!


Top
   
Display posts from previous:  Sort by  
Forum locked  This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC-06:00


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Limited