Restore process cancelled at migrating uploads to S3 step

Unterstützung
22

If you need any help with drilling down to the root cause of issues like this, please let me know. I’m happy to help.

5 „Gefällt mir“
23

So, tried to restore my 2.2GB backup and got this - the restore failed:

EXCEPTION: 44 posts are not remapped to new S3 upload URL. S3 migration failed for db ‘default’.

I am on the 2.6b6, so a fairly recent version. The site is fairly old, from 2016.

From time to time we run into backups were the automatic remapping and migration to S3 fails for various reasons.

This is an old topic, so any recommendation for corrective action? Having a backup I can’t actually use to restore makes me a little nervous.

Edit: I just realized I may be in the wrong thread, as this seems like the same issue

1 „Gefällt mir“
24

@gerhard

Gave this another shot and I am still failing on the restore to the 44 posts are not remapped -error.

Temporary disabling of S3 uploads prior to the backup (proposed by @RGJ does not solve the issue, and currently I don’t have a working backup scheme, which is pretty damn serious.

Any suggestions on what to try?

25

Okay, this is the weirdest case I’ve seen so far. I stumpled upon this post.

https://meta.discourse.org/t/using-object-storage-for-uploads-s3-clones/148916/160?u=ljpp

After wasting hours on this already, I defined the DISCOURSE_CDN_URL just for kicks, a feature my site does not use. The backup was restored successfully.

What is the significance of this parameter, in this scenario? @Falco @pfaffman

EDIT:

I take that back. After success with the test, I took a fresh backup from production and once again started to migrate to a new server. It failed again, but the error message changed.

EXCEPTION: rake posts:missing_uploads identified 3 issues. S3 migration failed for db ‘default’.

EDIT2:

So I kept drilling the database and found these 3 posts.

  • 2 were very old images, that were first published but then moderator replaced the images with a modified version. These were from 2016 and 2018.
  • But the last 1 was odd. It was a very recent post just a couple of weeks ago by myself and it contained a oneboxed https:// link to a development server, that no longer exists. So a broken link breaks the restore process.

I simply deleted these posts manually.

Now, again, a test run shows that a backup might actually succeed. We’ll see.

2 „Gefällt mir“
26

@ljpp I seem to be in a similar situation with a restore failing with

EXCEPTION: 1 posts are not remapped to new S3 upload URL. S3 migration failed for db ‘default’.

Can you elaborate on how you found and deleted the offending posts? What commands are used?

1 „Gefällt mir“
27

He deleted the posts in question.

But you wiped your install so you can’t do that, right?

1 „Gefällt mir“
29

Ich habe dieses Problem beim Wiederherstellen meiner Datenbank. Wie haben Sie die beanstandeten Beiträge gefunden?

30

Ich denke, der Code, der die Überprüfung durchführt, befindet sich hier:

Also denke ich, das hier:

prefix = @migrate_to_multisite ? "uploads/#{@current_db}/original/" : "original/"
base_url = File.join(SiteSetting.Upload.s3_base_url, prefix)
bad = Upload.by_users.where("url NOT LIKE '#{base_url}%'")

Und zur Sicherheit

good = Upload.by_users.where("url LIKE '#{base_url}%'")

Lass mich wissen, ob das für dich funktioniert, und ich werde sehen, ob ich ein Thema erstellen kann.

1 „Gefällt mir“
31

discourse(prod) > prefix = @migrate_to_multisite ? “uploads/#{RailsMultisite::ConnectionManagement.current_db}/original/” : “original/”
discourse(prod) > base_url = File.join(SiteSetting.Upload.s3_base_url, prefix)
discourse(prod) > bad_uploads = Upload.by_users.where(“url NOT LIKE ‘#{base_url}%’”)
discourse(prod) > bad_uploads.count
=> 0

Dieser Check ergab bei mir 0 Fehler

32

Haben Sie das auf dem ursprünglichen Server gemacht? Oder müssen Sie es tun, nachdem die Datenbank wiederhergestellt wurde, bevor sie diese Prüfung durchführt, indem Sie die Option --pause verwenden?

33

Ich habe es auf dem alten Server gemacht.
Beim Wiederherstellen erhielt ich denselben Fehler

[2026-01-16 13:45:52] EXCEPTION: 3 Beiträge werden nicht auf die neue S3-Upload-URL umgeordnet. S3-Migration für die Datenbank „default“ fehlgeschlagen.
[2026-01-16 13:45:52] /var/www/discourse/lib/file_store/to_s3_migration.rb:132:in `raise_or_log’

34

Nun. Verdammt. Ich weiß nicht, was ich dir sonst noch sagen soll.

Hat der good deine Uploads gefunden?

Ich würde wahrscheinlich einfach den --pause-Schalter verwenden und die Wiederherstellung stoppen, bevor er diese Überprüfung durchführt.

Ich würde tun, was Richard gesagt hat.

1 „Gefällt mir“
35

Ich bin mir Ihrer genauen Situation nicht sicher, aber Sie möchten möglicherweise einfach die S3-Uploads deaktivieren, das Backup erstellen, wiederherstellen und sie wieder aktivieren. Das hat mir schon oft geholfen.

1 „Gefällt mir“