- 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.

My added script:
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