Jump to content
  • [6.6.4] No cron job running during the night


    Niklas
    • 6.6.5 Solved Urgent

    Hello,

     

    I have some cron jobs running during the night and morning every day. None of my cron job has run over the night, upgraded to 6.6.4 yesterday. No mover, no added backup script (using User Scripts), no daily trim and no Backup / Restore from CA.

    cat /etc/cron.d/root
    # Generated docker monitoring schedule:
    10 */6 * * * /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:
    0 3 * * * /usr/local/sbin/mover |& logger
    
    # Generated plugins version check schedule:
    10 */6 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null
    
    # Generated Unraid OS update check schedule:
    11 */6 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null
    
    # Generated ssd trim schedule:
    5 4 * * * /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

     

    root@Server:/etc# cd cron.daily/
    root@Server:/etc/cron.daily# v
    total 12
    -rwxrwxrwx 1 root root  76 Nov  8 00:08 fix.common.problems.sh*
    -rwxr-xr-x 1 root root 129 Apr 13  2018 logrotate*
    -rwxrwxrwx 1 root root  76 Nov  8 00:08 user.script.start.daily.sh*
    root@Server:/etc/cron.daily# cd ..
    root@Server:/etc# cd cron.hourly/
    root@Server:/etc/cron.hourly# v
    total 4
    -rwxrwxrwx 1 root root 77 Nov  8 00:08 user.script.start.hourly.sh*
    root@Server:/etc/cron.hourly# cd ../cron.weekly/
    root@Server:/etc/cron.weekly# v
    total 4
    -rwxrwxrwx 1 root root 77 Nov  8 00:08 user.script.start.weekly.sh*
    root@Server:/etc/cron.weekly# cd ../cron.monthly/
    root@Server:/etc/cron.monthly# v
    total 4
    -rwxrwxrwx 1 root root 78 Nov  8 00:08 user.script.start.monthly.sh*
    root@Server:/etc/cron.monthly#

    Just added my own backup script using "User Scripts" lately. No more, no less. :)

     

    Stuff supposed to be running here, nothing, except for fix common problems but that might be because of reboot after upgrade to .4.

    Capture_System_Log_-_Google_Chrome_2018-11-08_11-04-26_01625183.png.0a6dbbe1e710cbccd7b0c17daf618c4e.png

     

    Server%2FScheduler.png

     

    My added script:

    Capture_ServerUserscripts_-_Google_Chrome_2018-11-08_11-07-29_03478224.thumb.png.b87b62703aa3d5ab7502455368b67186.png

    Contents:

    #!/bin/bash
    cd /mnt/user/AppdataBackup
    /usr/local/bin/duplicacy prune -keep 0:5
    /usr/local/bin/duplicacy prune
    /usr/local/bin/duplicacy backup -stats -hash

     

    • Like 2


    User Feedback

    Recommended Comments






    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.