Backup failed: Archive XXXXXXX already exists

[ghubz]

Hi,

Out of a sudden I keep getting "Backup failed"
Creating archive at "/home/weblate/backups/::{now}"
Archive 2021-05-10T02:00:00 already exists

Manually running the backup works fine.

I am running the latest version 4.6.2.

Any ideas?

Thanks in advance!

[nijel]

Most likely there were two backups triggered at the same time. Maybe your Celery beat scheduler is running twice?

[ghubz]

Thanks for the prompt reply. May I ask how I can check that?

[nijel]

Check running processes. There should be single toplevel process executed with --beat. It is okay to have a number of child processes there, for example:

# ps faux | grep celery.*beat
root      7825  0.0  0.0   6152   888 pts/0    S+   13:29   0:00          \_ grep celery.*beat
weblate  28586  0.3  4.0 356936 158996 ?       S    May08   9:54 /home/weblate/weblate-env/bin/python3 -m celery -A weblate.utils worker --pidfile=/run/celery/weblate-celery.pid --logfile=/var/log/celery/weblate-celery%I.log --loglevel=INFO --beat --queues=celery --prefetch-multiplier=4 -n celery@lime-weblate --executable=/home/weblate/weblate-env/bin/python3
weblate  28671  0.0  3.3 357780 133144 ?       S    May08   0:24  \_ /home/weblate/weblate-env/bin/python3 -m celery -A weblate.utils worker --pidfile=/run/celery/weblate-celery.pid --logfile=/var/log/celery/weblate-celery%I.log --loglevel=INFO --beat --queues=celery --prefetch-multiplier=4 -n celery@lime-weblate --executable=/home/weblate/weblate-env/bin/python3
weblate  28677  0.0  3.8 437096 153060 ?       Sl   May08   1:06  \_ /home/weblate/weblate-env/bin/python3 -m celery -A weblate.utils worker --pidfile=/run/celery/weblate-celery.pid --logfile=/var/log/celery/weblate-celery%I.log --loglevel=INFO --beat --queues=celery --prefetch-multiplier=4 -n celery@lime-weblate --executable=/home/weblate/weblate-env/bin/python3
weblate  28680  0.0  4.0 447580 161136 ?       Sl   May08   0:45  \_ /home/weblate/weblate-env/bin/python3 -m celery -A weblate.utils worker --pidfile=/run/celery/weblate-celery.pid --logfile=/var/log/celery/weblate-celery%I.log --loglevel=INFO --beat --queues=celery --prefetch-multiplier=4 -n celery@lime-weblate --executable=/home/weblate/weblate-env/bin/python3

[ghubz]

There are multiple top level ones. Maybe it has to do with the fact that I did celery stop + start multiple times, even though it doesn't really make much sense to be the reason? :/

[nijel]

It should detect that the process is already running and not start it again (unless you deleted the PID files).