edited
edited
edited
edited
edited
crontab -e -u hestiaweb
There is a task to run the backup:
10 03 * * * sudo /usr/local/hestia/bin/v-backup-users
You can edit the startup time to suit your needs.
Also check if the cron service is running - service cron status
edited
show output of crontab -l -u hestiaweb
edited
Look at the logs - /var/log/hestia/backup.log
edited
Run
/usr/local/hestia/bin/v-backup-users
in console
edited
There are no problems according to the logs. Most likely you have 1 backup copy that is saved. Change the settings in the package.
edited
Judging by everything you gave, everything should work. Unfortunately, if I need to look at your server, it is already paid for on my part. Since it is my time. The answers on this forum are advisory in nature.
edited
That means it will run at 03:01.
Show the output of these commands:
grep 'CRON.*v-backup' /var/log/syslog
cat /etc/sudoers.d/hestiaweb
exim4 -bp
2 Likes
edited
Can you see any other CRON entries in syslog?
grep CRON /var/log/syslog | tail -n15
If you can’t see any entry:
apt update
apt full-upgrade
apt autoremove
apt clean
apt reinstall cron
And try to run a cron job again modifying the time execution for that cron job.
edited
cron is working.
Show the output of these commands:
namei -mo /var/spool/cron/crontabs/hestiaweb
cat -A /var/spool/cron/crontabs/hestiaweb
edited
The permissions are correct, and the contents of the crontab are fine… Well, I’m missing a few scripts there, but it should work with the ones you have.
Just in case, reboot your server if you haven’t already done so.