Schedule server still doesn't work as expected? 16.1

[raidsm]

Hi Jocko!

as asked:

Sorry I did not understand you rightly.

So I need some output:

enable the debug mode

done

set a job with a bigger value ~10min

done: set to go at 20H40 standby of 10 minutes

and post the content of /var/log/messages before standby(so do not plan the standby too soon)

see attachement

after waking up post the content of /boot.log

see attachement

disable the debug mode

done

Before running this test, post

Code: Select all

ls -l /sbin/rebootd-spd
grep suspend /etc/inc/global_defs.inc

I did it near 20H28...

root@NS2:/ # ls -l /sbin/rebootd-spd
lrwxrwxrwx 1 root root 22 2016-03-01 06:57 /sbin/rebootd-spd -> /bin_cab/rebootd-nwsp2
root@NS2:/ # grep suspend /etc/inc/global_defs.inc
$shareStatus = array('active_share','suspended_share');
"echo -e \$(date +'%Y/%m/%d %T'): Standby with suspended time \(%s\)>>/direct-usb/cronjobs/cron.log && echo %s > /etc/time-suspend.txt && touch wol-enable && /sbin/rebootd-spd",
root@NS2:/ #

[Jocko]

Hi raidsm,

I think I have found the issue and indeed it is a bug (wrong cron command line for this feature).

I am pretty sure the feature works well if you do a Nas standby and auto-wakeup from the Shutdown/Restart menu.

We go to try to fix the bad cron command line. In a putty window do

Code: Select all

sed -rie 's;(.*)touch wol-enable(.*);\1touch /etc/wolenable\2;g' /etc/inc/global_defs.inc

Then try again to set this cron job. Now it should work

[raidsm]

You where right. From the start/shutdown menu the command work well

did the sed command and Voila! ;) the cron command to sleep now works great. I'm curious I'm the only one who report this bug?

BTW I've read somewhere that this was don't have a "true" WOL or suspend mode. How about the power consumption if not a "real" power management? Does it even worth it to take the NAS into "stand-by" mode or either a complete shutdown with manual power up in the morning OR just leave it powered on is about the same?

What do you think?

[Jocko]

Hi raidsm,

Yes you are the first member who reported this issue.

What is amazing, another member has reported a bug on this feature (and I did a patch for that) but he seems not to have an auto wakeup just after standdy. I checked and the wrong cron command line is present with the unpatched version 16.1 and also with the patch.

So he had to have the same issue :scratch

I've read somewhere that this was don't have a "true" WOL or suspend mode. How about the power consumption if not a "real" power management? Does it even worth it to take the NAS into "stand-by" mode or either a complete shutdown with manual power up in the morning OR just leave it powered on is about the same?

when you switch off the NAS or standby it from the web-interface you really stop the power consumption.

If you use WOL feature, you need for these platforms to keep on the system card. So the difference is only the disk power consumption