Okay this was bound to happen, things were just too good for too long. Years of running on cruise control, the system would automatically update itself and I would update Discourse every few weeks. At midnight last night, Amazon showed the system was unresponsive, discourse was down and the CPU was …

Thanks, my site has crashed unfortunately so I’m only left with the S3 uploads and back ups. I’m assuming there’s no way to for me to migrate any left over local files to the S3 now. So I’m wondering what are my options right now? Is there a way to restore from S3 backups and ignore the local files…

So an update for folks who may be struggling with the same issue (basically I’m unable to restore from a backup and the server crashed due to a fault system upgrade). From what I understand the root cause of the issue is that there are local uploads AND there are S3 uploads, so when the restore too…

If you configure as described in Using Object Storage for Uploads (S3 & Clones) you should be able to rake uploads:migrate_to_s3 If you want to stop using s3, then you can enter the rails console and set SiteSetting.include_s3_uploads_in_backups=true Then take a backup, make sure that you do n…

Okay I think I got a little mixed up here. I’m thinking the ideal thing to do would probably be to have all uploads local and save the backups (zips) to the S3. This way the backup is available on S3 should anything happen to the server but the backup in itself is self contained with no dependencie…

[afbeelding] RBoy: This is the part that confused me, why would I want to put the S3 configuration in the app.yml file? So that you have access to your backups via a command line restore before you restore your backup. Otherwise, you have to set up an admin account and then configure S3 and t…

[afbeelding] RBoy: why would I want to put the S3 configuration in the app.yml file? Because you will have trouble restoring otherwise.

[afbeelding] Richard - Communiteq: Because you will have trouble restoring otherwise. How would one restore a backup from S3 using the command line? According to the instructions here: Restore a backup from the command line It says you can drop the backup file into the /var/discourse/shared/…

cd /var/discourse ./launcher enter app discourse restore It’ll print the available backups you can then copy/paste the one that you want to do the restore.

Thanks, so it’ll read the S3 backups and list them an option. Jay, to follow up on a suggestion you had made to move assets local: I think you can set a hidden setting include_s3_uploads_in_backups to true and then make a backup and restore it when s3 is turned off to stop using S3. Having S3 ba…

Well, atleast I figured out why my server crashed last night (and again today after a complete rebuild :frowning: , see this topic for details: Ubuntu 20.04 kernel update with docker causing a crash

Hulp bij herstel - systeem bleef hangen om middernacht

Ondersteuning Installatie

pfaffman (Jay Pfaffman) 10 juni 2022 om 00:42 24

Rebake all posts matching a pattern

Topic		Antwoorden	Weergaven
Restore failed at "EXCEPTION: x of y uploads are not migrated to S3. S3 migration failed for db 'default'." Self-hosting	4	1093	10 juni 2022
Restore process cancelled at migrating uploads to S3 step Support	49	2861	24 januari 2026
Intended path to migrate S3 to local Self-hosting uploads , s3	5	837	13 mei 2023
Restore to New Host Support	13	628	15 januari 2026
Implosion after 2.7beta7 upgrade Support	18	1249	27 april 2021

Hulp bij herstel - systeem bleef hangen om middernacht

Gerelateerde topics