Autoshutdown restarts OMV one time

kyz3 · Apr 19th 2017

Hi,

as some others, i have one problem with the autoshutdown-plugin.
I have it set up and it works how i want with one major quirk i cant seem to figure out:

Every evening, when omv is supposed to go to sleep (hibernate) it reboots one time, the second time autoshutdown issues the hibernate command it works as intended.

The logs seem to be correct and i can see no errors, or falsely issued commands:

Code: autoshutdown.log

Apr 19 00:40:57 omv logger: autoshutdown[28068]: INFO: ' new supervision cycle started - check active hosts or processes'
Apr 19 00:40:57 omv logger: autoshutdown[28068]: INFO: ' Checking the time: stay up or shutdown ...'
Apr 19 00:40:57 omv logger: autoshutdown[28068]: INFO: ' System is in Shutdown-Range. Do further checks ...'
Apr 19 00:40:57 omv logger: autoshutdown[28068]: INFO: ' retrieve list of active IPs for 'eth0' ...'
Apr 19 00:40:58 omv logger: autoshutdown[28068]: INFO: ' No active IPs in the specified IP-Range found'
Apr 19 00:40:58 omv logger: autoshutdown[28068]: INFO: ' Check Connections for 'eth0''
Apr 19 00:40:59 omv logger: autoshutdown[28068]: INFO: ' ULDL-Traffic-Check for 'eth0''
Apr 19 00:40:59 omv logger: autoshutdown[28068]: INFO: ' eth0: over the last 300 seconds: DL: 0.0 kB/s; UL: 0.0 kB/s'
Apr 19 00:40:59 omv logger: autoshutdown[28068]: INFO: ' eth0: UL- and DL-Rate is under 50 kB/s -> next check'
Apr 19 00:40:59 omv logger: autoshutdown[28068]: INFO: ' HDD-IO: '/dev/sda -> backup2' (last 300s): r: 0.0 w: 0.0 is under 401 -> next HDD'
Apr 19 00:40:59 omv logger: autoshutdown[28068]: INFO: ' HDD-IO: '/dev/sdb -> ' (last 300s): r: 0.0 w: 7.3 is under 401 -> next HDD'
Apr 19 00:40:59 omv logger: autoshutdown[28068]: INFO: ' HDD-IO: '/dev/sdc -> media1' (last 300s): r: 0.0 w: 0.0 is under 401 -> next HDD'
Apr 19 00:40:59 omv logger: autoshutdown[28068]: INFO: ' HDD-IO: '/dev/sdd -> backup1' (last 300s): r: 0.0 w: 0.0 is under 401 -> next HDD'
Apr 19 00:40:59 omv logger: autoshutdown[28068]: INFO: ' HDD-IO: '/dev/sde -> media2' (last 300s): r: 0.0 w: 0.0 is under 401 -> next HDD'
Apr 19 00:40:59 omv logger: autoshutdown[28068]: INFO: ' HDD-IO all checks for HDD-IO finished'
Apr 19 00:41:03 omv logger: autoshutdown[28068]: INFO: ' No active hosts or processes within network range, 0 cycles until shutdown...'
Apr 19 00:41:03 omv logger: autoshutdown[28068]: INFO: ' Shutdown issued: 'pm-hibernate''
Apr 19 00:41:03 omv logger: autoshutdown[28068]: INFO: '   '
Apr 19 00:41:03 omv logger: autoshutdown[28068]: INFO: '   '
Apr 19 00:42:01 omv autoshutdown.sh[12778]: logger: autoshutdown[12778]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
Apr 19 00:42:01 omv autoshutdown.sh[12778]: logger: autoshutdown[12778]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
Apr 19 00:42:01 omv autoshutdown.sh[12778]: logger: autoshutdown[12778]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
Apr 19 00:42:01 omv autoshutdown.sh[12778]: logger: autoshutdown[12778]: INFO: ' X Version: 0.9.9.10'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' X Version: 0.9.9.10'
Apr 19 00:42:01 omv autoshutdown.sh[12778]: logger: autoshutdown[12778]: INFO: ' Initialize logging to local6'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' Initialize logging to local6'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' /etc/autoshutdown.conf loaded'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' ------------------------------------------------------'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' Checking config'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' LOADPROCNAMES is set to: 'smbd,nfsd,transmission-daemon,mt-daapd,forked-daapd' (default)'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' TEMPPROCNAMES is disabled - No processes being checked'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' SHUTDOWNCOMMAND is set to 'pm-hibernate''
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' Your Kernel supports the following modes from pm-utils:'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' Kernel supports SUSPEND (SUSPEND to RAM)'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' Kernel supports HIBERNATE (SUSPEND to DISK)'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' Kernel supports HYBRID-SUSPEND (to DISK & to RAM)'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: WARN: ' LOADAVERAGECHECK is set to false'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: WARN: ' Ignoring LOADAVERAGE'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' ------------------------------------------------------'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' Reading NICs ,IPs, ...'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' NIC 'bond0' not found, skipping 'bond0''
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' NIC 'eth0' found: try to get IP'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' _check_networkconfig(): Run: #1: IP-Adress found'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' 'eth0' has IP: 192.168.0.10'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' NIC 'eth1' not found, skipping 'eth1''
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' Pinglist deleted'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: '---------------- script started ----------------------'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' 5 test cycles until shutdown is issued.'
Apr 19 00:42:01 omv logger: autoshutdown[12778]: INFO: ' Waiting 5 min until the first check'

Display More

This is the autoshutdown.log. As you can see, the last active host (me) went offline at around 00:00, 5 cycles after ~00:30 (00:41:03 in this case) autoshutdown issues the "pm-hibernate" command.
Then the machine reboots! and the autoshutdown script is started again (00:42:01) goes 5 cycles, as nothing is online etc. and then issues another "pm-hibernate", this time the machine stays in hibernation until it is woken the next day.

Code: syslog.log

Apr 19 00:39:01 omv CRON[11918]: (root) CMD (  [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Apr 19 00:41:03 omv autoshutdown.sh[28068]: - : autoshutdown [28068]: INFO: Shutdown issued: 'pm-hibernate'
Apr 19 00:41:03 omv  - : autoshutdown [28068]: INFO: Shutdown issued: 'pm-hibernate'
Apr 19 00:41:03 omv systemd[1]: Expecting device dev-disk-by\x2duuid-6f943a1d\x2d6cb0\x2d4b11\x2da069\x2dc4650010a4f0.device...
Apr 19 00:41:03 omv systemd[1]: Starting Run anacron jobs...
Apr 19 00:41:03 omv systemd[1]: Started Run anacron jobs.
Apr 19 00:41:03 omv anacron[12514]: Anacron 2.3 started on 2017-04-19
Apr 19 00:41:03 omv anacron[12514]: Will run job `cron.daily' in 5 min.
Apr 19 00:41:03 omv anacron[12514]: Jobs will be executed sequentially
Apr 19 00:41:03 omv systemd[1]: Stopping Run anacron jobs...
Apr 19 00:41:03 omv systemd[1]: Stopped Run anacron jobs.
Apr 19 00:41:03 omv  autoshutdown [12650]: hibernate/suspend: autoshutdown-script stop from /etc/pm/sleep.d/autoshutdown-restart
Apr 19 00:42:01 omv kernel: [68209.738105] PM: Syncing filesystems ... 
Apr 19 00:42:01 omv kernel: [68209.748603] done.

Display More

In the syslog you can see autoshutdown puts an info (00:41:03) that pm-hibernate has been issued.
At 00:41:03 it shuts down after calling the stop function from the /etc/pm/sleep.d/autoshutdown-restart script (which is for logging purposes as far as i can tell).

This happens consistently.

Can anyone help me find the reason for the rebooting ?

kyz3 · May 5th 2017

No input at all ?

If any info is missing ill gladly provide this.

ryecoaaron · May 5th 2017

This is can be caused by a couple of things:

- bios: try updating your bios. acpi implementation on some systems is bad
- bios settings: some bios settings can effect and they are usually acpi related.

kyz3 · May 6th 2017

Hi ryecoaaron,

thanks for you reply.
Unfortunately i have no BIOS updates available, my system is already running on the latest version.

I will still take a look through the settings and see if anything has changed and report back.

Autoshutdown restarts OMV one time

Participate now!

Tags