No backup (latest.sql.gz) creation after upgrade to 4.0.x

CMS Version

4.0.3 / 4.0.4 (Ubuntu Server 22.04 LTS / docker install)

Player Type


Player Version



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

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


well spotted, and yes I can confirm that there is problem with the cron schedule in the fallowing file: /etc/cron.d/cms_backup_cron

Cause of the problem
above file is missing one mandatory field (for day): " Cron expressions consist of five mandatory fields and one optional field"

so in the above file we have this (incorrect crond does not understand this expression):
*/15 * * * root /etc/periodic/15min/cms-db-backup > /dev/null 2>&1

it should be:
*/15 * * * * root /etc/periodic/15min/cms-db-backup > /dev/null 2>&1

Temporary fix: for reported problem
For now I used docker cp to copy incorrect file from container to host machine, fixed the cron schedule exporession and copied back the correct file to docker container, look at docker cp on the docker page

Other tasks
cms_maintenance_cron runs correctly every 1minutes as the cron expression is correct (you can see this is web container logs)

it would be nice to fix this in the next release

Best Regards
Grzegorz Agacinski

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.