clevoir Posted October 2, 2015 Share Posted October 2, 2015 I am running 6.1.3 and have found that my monthly parity check is no longer working. I first noticed this when I updated from 6.1. to 6.1.1 Quote Link to comment
bonienl Posted October 2, 2015 Share Posted October 2, 2015 I am running 6.1.3 and have found that my monthly parity check is no longer working. I first noticed this when I updated from 6.1. to 6.1.1 Due to security enhancements introduced in unRAID v6.1 you need to re-apply the parity check settings if you upgraded previously from unRAID v6.0. Quote Link to comment
Tarsier Posted October 3, 2016 Share Posted October 3, 2016 I upgraded from 5.05 to 6.2 and also noticed that my monthly parity check didn't run on the 1st of the month. I tried to upgrade using the automated plugin but it wouldn't boot after so I copied the syslinux folder over from the latest zip and ran make_bootable.bat I've tried disabling and re-enabling both notifications and the monthly parity check in Scheduler but the cron job doesn't appear. I noticed that when I disable the scheduled monthly parity check and re-enable the following message appears briefly at the bottom of the Scheduler page Warning: unlink(/tmp/memory.tmp): No such file or redirectory in /usr/local/emhttp/plugins/dynamix/include/update.parity.php on line 55 EDIT: Thought that a scheduled cron job for backup to external hdd not working may have been related, but it is now working Quote Link to comment
bonienl Posted October 3, 2016 Share Posted October 3, 2016 I upgraded from 5.05 to 6.2 and also noticed that my monthly parity check didn't run on the 1st of the month. I tried to upgrade using the automated plugin but it wouldn't boot after so I copied the syslinux folder over from the latest zip and ran make_bootable.bat I've tried disabling and re-enabling both notifications and the monthly parity check in Scheduler but the cron job doesn't appear. I noticed that when I disable the scheduled monthly parity check and re-enable the following message appears briefly at the bottom of the Scheduler page Warning: unlink(/tmp/memory.tmp): No such file or redirectory in /usr/local/emhttp/plugins/dynamix/include/update.parity.php on line 55 EDIT: Thought that a scheduled cron job for backup to external hdd not working may have been related, but it is now working When you enable the parity schedule, do the settings "stick" after apply? Quote Link to comment
Tarsier Posted October 3, 2016 Share Posted October 3, 2016 The settings stick on the Scheduler settings page, yes However, when i run cat /var/spool/cron/crontabs/root the parity check does not appear # 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 Quote Link to comment
Squid Posted October 3, 2016 Share Posted October 3, 2016 The settings stick on the Scheduler settings page, yes However, when i run cat /var/spool/cron/crontabs/root the parity check does not appear What about cat /etc/cron.d/root Quote Link to comment
Tarsier Posted October 3, 2016 Share Posted October 3, 2016 I get the output below # Custom cron scripts: # Runs Docs Backups on Tue and Fri 2am 0 2 0 * 2 logger Started DocsBackupTue && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsTue/ 2>&1 1>/dev/null 0 2 0 * 5 logger Started DocsBackupFri && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsFri/ 2>&1 1>/dev/null# Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated parity check schedule: 0 0 * * 0 /usr/local/sbin/mdcmd check &> /dev/null # Generated plugins version check schedule: 10 0 1 * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null Quote Link to comment
Squid Posted October 3, 2016 Share Posted October 3, 2016 I get the output below # Custom cron scripts: # Runs Docs Backups on Tue and Fri 2am 0 2 0 * 2 logger Started DocsBackupTue && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsTue/ 2>&1 1>/dev/null 0 2 0 * 5 logger Started DocsBackupFri && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsFri/ 2>&1 1>/dev/null# Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated parity check schedule: 0 0 * * 0 /usr/local/sbin/mdcmd check &> /dev/null # Generated plugins version check schedule: 10 0 1 * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null Well, it's set to run which unfortunately puts this issue squarely in the hands of bonienl/limetech Quote Link to comment
Tarsier Posted October 3, 2016 Share Posted October 3, 2016 I played around with the Scheduler settings page I seem to have gotten it working now # Custom cron scripts: # Runs Docs Backups on Tue and Fri 2am 0 2 0 * 2 logger Started DocsBackupTue && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsTue/ 2>&1 1>/dev/null 0 2 0 * 5 logger Started DocsBackupFri && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsFri/ 2>&1 1>/dev/null# Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated parity check schedule: 0 0 1 * * /usr/local/sbin/mdcmd check &> /dev/null # Generated plugins version check schedule: 10 0 1 * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null I would guess that it's related to the way the Scheduler settings page refreshes when you select Scheduled parity check setting i.e. when you select Monthly, the page refreshes to give the monthly settings, but you need to actually change the settings, for them to be updated. Selecting Apply immediately after selecting Monthly, doesn't change the cron settings correctly. Hope that makes sense? Quote Link to comment
Squid Posted October 3, 2016 Share Posted October 3, 2016 I played around with the Scheduler settings page I seem to have gotten it working now # Custom cron scripts: # Runs Docs Backups on Tue and Fri 2am 0 2 0 * 2 logger Started DocsBackupTue && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsTue/ 2>&1 1>/dev/null 0 2 0 * 5 logger Started DocsBackupFri && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsFri/ 2>&1 1>/dev/null# Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated parity check schedule: 0 0 1 * * /usr/local/sbin/mdcmd check &> /dev/null # Generated plugins version check schedule: 10 0 1 * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null I would guess that it's related to the way the Scheduler settings page refreshes when you select Scheduled parity check setting i.e. when you select Monthly, the page refreshes to give the monthly settings, but you need to actually change the settings, for them to be updated. Selecting Apply immediately after selecting Monthly, doesn't change the cron settings correctly. Hope that makes sense? That would be a defect in my mind Quote Link to comment
bonienl Posted October 4, 2016 Share Posted October 4, 2016 I played around with the Scheduler settings page I seem to have gotten it working now # Custom cron scripts: # Runs Docs Backups on Tue and Fri 2am 0 2 0 * 2 logger Started DocsBackupTue && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsTue/ 2>&1 1>/dev/null 0 2 0 * 5 logger Started DocsBackupFri && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsFri/ 2>&1 1>/dev/null# Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated parity check schedule: 0 0 1 * * /usr/local/sbin/mdcmd check &> /dev/null # Generated plugins version check schedule: 10 0 1 * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null I would guess that it's related to the way the Scheduler settings page refreshes when you select Scheduled parity check setting i.e. when you select Monthly, the page refreshes to give the monthly settings, but you need to actually change the settings, for them to be updated. Selecting Apply immediately after selecting Monthly, doesn't change the cron settings correctly. Hope that makes sense? I tested this but for me this is working correctly. You can disable the scheduler which removes the cron file and setting, and after changing it to monthly it is added as expected when pressing Apply. Are you running perhaps an adblocker, if so then whitelist the GUI. Quote Link to comment
Tarsier Posted October 4, 2016 Share Posted October 4, 2016 Bizarrely enough, it seems to be working fine now. No adblockers installed... Quote Link to comment
bonienl Posted October 5, 2016 Share Posted October 5, 2016 Bizarrely enough, it seems to be working fine now. No adblockers installed... Do you mind setting this as 'solved'. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.