unRAID OS Version:

6.0b13

Description:

If the scheduler is enabled / running, when you reboot it will revert back to a stopped status, and the cron entry for monthly parity checks will disappear.  Originally reported in b12 here: http://lime-technology.com/forum/index.php?topic=37429.0

How to reproduce:

Enable the scheduler, run

cat /var/spool/cron/crontabs/root

, reboot and run it again. 

 

Expected results:

Scheduler to be enabled

 

Other information:

 

cat /var/spool/cron/crontabs/root
# If you don't want the output of a cron job mailed to you, you have to direct
# any output to /dev/null.  We'll do this here since these jobs should run
# properly on a newly installed system.  If a script fails, run-parts will
# mail a notice to root.
#
# Run the hourly, daily, weekly, and monthly cron jobs.
# Jobs that need different timing may be entered into the crontab as before,
# but most really don't need greater granularity than this.  If the exact
# times of the hourly, daily, weekly, and monthly cron jobs do not suit your
# needs, feel free to adjust them.
#
# Run hourly cron jobs at 47 minutes after the hour:
47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null
#
# Run daily cron jobs at 4:40 every day:
40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null
#
# Run weekly cron jobs at 4:30 on the first day of the week:
30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null
#
# Run monthly cron jobs at 4:20 on the first day of the month:
20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null
# System data collection - poll every minute
*/1 * * * * /usr/lib/sa/sa1 1 1 1>/dev/null 2>&1
# Scheduled Parity Check
0 0 1 * * /root/mdcmd check  1>/dev/null 2>&1
root@Server_B:~#
Broadcast message from root@Server_B (Mon Feb 16 20:59:10 2015):

The system is going down for reboot NOW!
login as: root
[email protected]'s password:
Linux 3.18.5-unRAID.
root@Server_B:~# cat /var/spool/cron/crontabs/root
# If you don't want the output of a cron job mailed to you, you have to direct
# any output to /dev/null.  We'll do this here since these jobs should run
# properly on a newly installed system.  If a script fails, run-parts will
# mail a notice to root.
#
# Run the hourly, daily, weekly, and monthly cron jobs.
# Jobs that need different timing may be entered into the crontab as before,
# but most really don't need greater granularity than this.  If the exact
# times of the hourly, daily, weekly, and monthly cron jobs do not suit your
# needs, feel free to adjust them.
#
# Run hourly cron jobs at 47 minutes after the hour:
47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null
#
# Run daily cron jobs at 4:40 every day:
40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null
#
# Run weekly cron jobs at 4:30 on the first day of the week:
30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null
#
# Run monthly cron jobs at 4:20 on the first day of the month:
20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null
# System data collection - poll every minute
*/1 * * * * /usr/lib/sa/sa1 1 1 1>/dev/null 2>&1

Bonienl just posted up a "Band-Aid" which fixes this:

 

http://lime-technology.com/forum/index.php?topic=38193.msg354039#msg354039