Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

daily backup did not generate database.sql file in the backup folder #98

Closed
Jiansiyu opened this issue Oct 31, 2021 · 5 comments · Fixed by #104
Closed

daily backup did not generate database.sql file in the backup folder #98

Jiansiyu opened this issue Oct 31, 2021 · 5 comments · Fixed by #104

Comments

@Jiansiyu
Copy link

Thank you very much for the amazing project.

I noticed one issue. the auto daily backups in the backups folder. The database backup did not show in the tar.gz file.

@rafalp
Copy link
Owner

rafalp commented Oct 31, 2021

That's weird. It always worked for me (until it ran out of disk space for backups). Are you sure there's enough space?

@Jiansiyu
Copy link
Author

Jiansiyu commented Oct 31, 2021

There is only 37% of the space is used. It is weird. All the manual and Upgrade backups are normal.

These are three backup .gz files.

image

@rafalp
Copy link
Owner

rafalp commented May 25, 2023

I've checked random daily backup and indeed its missing database.sql

@rafalp
Copy link
Owner

rafalp commented May 30, 2023

Ok, I understand what's happening here.

Daily backup is done with crontab:

0 1 * * * cd /root/misago_docker && ./appctl daily_backup

./appctl tries to do docker-compose run --rm misago ./.run backup_db which fails for cron user because there's no docker-compose. So it tries run --rm misago ./.run backup_db.

@rafalp
Copy link
Owner

rafalp commented May 30, 2023

I've did a quick test and got following error:

./appctl: line 333: run: command not found

@rafalp rafalp mentioned this issue May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants