I have a backup script that runs daily. Each day is a different script.
On Sunday, I run /root/scripts/backup0.sh which is:
# /usr/sbin/virtualmin backup-domain --dest /root/backups0/ --all-domains --all-features --newformat --all-virtualmin
On Monday, /root/backups1/ and so on.
Here is the crontab entry:
1 1 * * 0 /root/scripts/backup0.sh 1 1 * * 1 /root/scripts/backup1.sh 1 1 * * 2 /root/scripts/backup2.sh 1 1 * * 3 /root/scripts/backup3.sh 1 1 * * 4 /root/scripts/backup4.sh 1 1 * * 5 /root/scripts/backup5.sh 1 1 * * 6 /root/scripts/backup6.sh
This used to work well on Debian 7, but very poorly on Debian 8. I have to run the scripts manually.
The backups tend to fail to errors every night, often the gzip of databases.
Where should I look for errors? Are the errors logged somewhere?
I also get some strange errors with the apt-get updates, again not in Debian 7 (that is from the daily cron job). Could this be related?
( apt-get -qq update && apt-get -qqy upgrade -u ) 2>&1 | tee -a /var/log/auto-upgrade.log
debconf: unable to initialize frontend: Dialog debconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (This frontend requires a controlling tty.) debconf: falling back to frontend: Teletype dpkg-preconfigure: unable to re-open stdin: dpkg: warning: 'ldconfig' not found in PATH or not executable dpkg: warning: 'start-stop-daemon' not found in PATH or not executable dpkg: error: 2 expected programs not found in PATH or not executable Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin E: Sub-process /usr/bin/dpkg returned an error code (2)
I rebuilt from a clean Debian 8, adding Virtulamin and then the domains.
I switched from mysql to MariaDB.