No backup files (latest.sql.gz) are created

[Landgraf]

After Xibo Upgrade from 3.3.8 to 4.0.3 no backup files (latest.sql.gz) are created under …/shared/backup/db. It seems to be that no cron jobs are executing within the docker container.

- I can run a manual mysqldump without errors and the file is then created.
(mysqldump -u cms -h mysql -p cms | gzip > /var/www/backup/db/latest.sql.gz)

- I can run the cron job “cms-db-backup” in folder “/etc/periodic/15min/” and the file is then created

=> But no file will be created every 24h or after docker start

The problem exists after upgrade from 4.0.3 to 4.0.4 .

Please give me instructions, how to check what the problem could be?
Could it be that other cron jobs are also not executed within the container, not only the backup jobs?

[alex]

Thanks for your report.

I see the same issue and have logged a bug to get that resolved.

Docker: automatic database backups not running v4

In the meantime, you can patch the local container as follows:

docker-compose exec cms-web bash
apt update
apt install nano
nano /entrypoint.sh

edit line 235 and add an extra * character after the */15 so the whole line reads:

    echo "*/15 * * * * root /etc/periodic/15min/cms-db-backup > /dev/null 2>&1" > /etc/cron.d/cms_backup_cron

exit
docker-compose restart cms-web

A latest.sql.gz should pop out within 15 minutes or so.

[Landgraf]

Hello @alex , thank you very much for investigating the error and giving us the interim solution.
I think, there is a typo in your workaround. You have to patch and login into the cms-web container, not the cmd-db container.
You have to login with the command: docker-compose exec cms-web bash.
I found the issue in your mentioned entrypoint.sh file. Backup is now up and running.

[alex]

Thank you. I’ve corrected it now.