• 6.6.6 -- parity check schedule not working


    zoggy
    • Retest Annoyance

    about to update to 6.7.x and noticed that since I've been on 6.6.6 the cron job hasnt kicked off the parity check in a few months

    firefox_2019-01-22_12-50-05.png

     

    settings:

    firefox_2019-01-22_12-49-46.png

     

    crontab -l

    # crontab -l
    # 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
    0 11 * * 0 /usr/local/emhttp/plugins/ca.backup/scripts/backup.php &>/dev/null 2>&1
    

     

    cron.d/root

    # cat /etc/cron.d/root
    # Generated docker monitoring schedule:
    10 0 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null
    
    # Generated system monitoring schedule:
    */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
    
    # Generated mover schedule:
    5 8 * * 6 /usr/local/sbin/mover |& logger
    
    # Generated parity check schedule:
    30 1 22-31 * 4 [[ $(date +%e -d +7days) -le 7 ]] && /usr/local/sbin/mdcmd check  &> /dev/null || :
    
    # Generated plugins version check schedule:
    10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null
    
    # Generated unRAID OS update check schedule:
    11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null
    
    # Generated cron settings for docker autoupdates
    0 13 * * 0 /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1
    # Generated cron settings for plugin autoupdates
    0 0 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
    # Generated ssd trim schedule:
    5 9 * * 6 /sbin/fstrim -a -v | logger &> /dev/null
    
    # Generated system data collection schedule:
    */1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
    

     




    User Feedback

    Recommended Comments

    updated and re-applied.

    I can see that the parity check was updated to:

    # Generated parity check schedule:
    30 1 * * 4 [[ $(date +%e -d +7days) -le 7 ]] && /usr/local/sbin/mdcmd check  &> /dev/null || :
    

     

    and per crontab.guru it looks like it should be good now

    Link to comment

    for completeness,

     

    cron.d/root

    # cat /etc/cron.d/root
    # Generated docker monitoring schedule:
    10 0 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null
    
    # Generated system monitoring schedule:
    */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
    
    # Generated mover schedule:
    5 8 * * 6 /usr/local/sbin/mover |& logger
    
    # Generated parity check schedule:
    30 1 * * 4 [[ $(date +%e -d +7days) -le 7 ]] && /usr/local/sbin/mdcmd check  &> /dev/null || :
    
    # Generated plugins version check schedule:
    10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null
    
    # Generated unRAID OS update check schedule:
    11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null
    
    # Generated cron settings for docker autoupdates
    0 13 * * 0 /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1
    # Generated cron settings for plugin autoupdates
    0 0 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1
    # Generated ssd trim schedule:
    5 9 * * 6 /sbin/fstrim -a -v | logger &> /dev/null
    
    # Generated system data collection schedule:
    */1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
    

     

    Link to comment


    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.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.