My backups keep accumulating in /var/discourse/shared/standalone/backups/default even though they are uploaded to Amazon S3. Here’s my Discourse setup: [Discourse backups settings] Discourse backups: [discourse backups] Backups in the S3 bucket: [Screenshot 2022-12-01 at 8.50.24 AM] And th…

Any chance that the server reboots due to automatic updates of the host OS? They might happen while the upload to S3 is in progress. Is there anything in the logs of your OS? Maybe reset the backup_time_of_day site setting to the default value or a different time and see if the problem disappears.

This is a standard install , right? Is there a chance that the OS (or something else) is killing the backup process during the upload? Because even when there’s a backup failure, the local file should be deleted at the end of the process.

Yes, standard install on a DigitalOcean droplet, Ubuntu 16.04.7 LTS. Where would the relevant log be?

I used some S3 compatible service for a while that sometimes resulted in backups being left on the local drive, but it was intermittent. You’d look in /var/discourse/shared/standalone/logs/rails/production.log. It just run a command line backup and see if it has the and behavior.

Production logs only go back a week, so the older “undeleted” backups fall out of that range, but I’ll keep an eye on the future ones. The only backup error entry was this in the 11/30 log: Started GET "/.env.backup" for 3.236.147.46 at 2022-11-29 19:15:57 +0000 ActionController::RoutingError (No r…

I see a new undeleted backup in /var/discourse/shared/standalone/backups/default but nothing in the production.log. Nothing in the production_errors.log either. Where else could I look? P.S. I ran a backup from the CLI and the backup was successfully removed - I’ll try that a few more times to see …

Not having success reproducing the undeleted local backup via CLI, but it does keep happening once or twice a week during the nightly backup. I also don’t see any of the backup log output in production.log. Are you sure that’s where it’s written, @pfaffman ?

[Bild] omarfilip: Are you sure that’s where it’s written, @pfaffman ? I think it should be. When I had a similar problem with some other S3 service, I was unable to find errors in either Discourse or their service. And I gave up and switched to something different. But you’re using AWS, S3, …

I’ve tried looking like this: grep -r "Output file is stored on S3" /var/discourse as that phrase is the last line of the CLI backup output, but nothing is found.

No, current uptime is 36 days. I had suspected that the DigitalOcean droplet backup running concurrently might have been the cause, but that happens once a week and my undeleted backups occur more frequently than that. I’ll try a different backup_time_of_day. It was set to 2:00 UTC, so we’ll see if…

[Bild] Gerhard Schlager: Any chance that the server reboots due to automatic updates of the host OS? OOOOH! That’s a good one. That would explain it. I bet that’s it. And the middle of the night is a Good Time for both backups and reboots. It doesn’t quite explain why the problem went away w…

Lokale Backups werden nach dem Hochladen auf Amazon S3 nicht gelöscht

Unterstützung

omarfilip 1. Dezember 2022 um 18:10 3

Ja, Standardinstallation auf einem DigitalOcean-Droplet, Ubuntu 16.04.7 LTS. Wo wäre das relevante Log?

Thema		Antworten	Aufrufe
Discourse not cleaning-up local tmp backups after uploading to S3 Self-hosting backups , s3	6	477	16. Januar 2024
S3 daily backups issue? Discourse also keeps backups locally every 4 days and I don't know why Support backups , s3	2	724	11. März 2022
Backups go to s3, but still a few random local backups stored Self-hosting backups	2	81	10. August 2024
Backup location Announcements backups , new-feature	12	5237	14. März 2019
Configure automatic backups for Discourse Self-Hosting backups , how-to	44	303632	19. Mai 2026

Lokale Backups werden nach dem Hochladen auf Amazon S3 nicht gelöscht

Verwandte Themen