I’m trying to move uploads to s3 on a relatively busy site. Everything goes as planned except when I run rake uploads:migrate_to_s3, I am presented with the following error: Updating the URLs in the database... Removing old optimized images... Flagging all posts containing lightboxes for rebake... 2023 posts were flagged for a rebake rake aborted! FileStore::ToS3MigrationError: 1 of 9629 uploads are not migrated to S3. S3 migration failed for db 'default'. /var/www/discourse/lib/file_store/to_s3_migration.rb:132:in `raise_or_log' /var/www/discourse/lib/file_store/to_s3_migration.rb:79:in `migration_successful?' /var/www/discourse/lib/file_store/to_s3_migration.rb:373:in `migrate_to_s3' /var/www/discourse/lib/file_store/to_s3_migration.rb:66:in `migrate' /var/www/discourse/lib/tasks/uploads.rake:123:in `migrate_to_s3' /var/www/discourse/lib/tasks/uploads.rake:102:in `block in migrate_to_s3_all_sites' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rails_multisite-4.0.0/lib/rails_multisite/connection_management.rb:80:in `with_connection' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rails_multisite-4.0.0/lib/rails_multisite/connection_management.rb:90:in `each_connection' /var/www/discourse/lib/tasks/uploads.rake:100:in `migrate_to_s3_all_sites' /var/www/discourse/lib/tasks/uploads.rake:96:in `block in ' /usr/local/bin/bundle:23:in `load' /usr/local/bin/bundle:23:in ` ' Tasks: TOP => uploads:migrate_to_s3 (See full trace by running task with --trace) This line in particular caught my attention FileStore::ToS3MigrationError: 1 of 9629 uploads are not migrated to S3. S3 migration failed for db 'default'. I’m assuming it means there is one problematic file that is causing the entire take task to fail? is there a way to figure out which file is causing the problem and maybe just remove it so the rest of the task completes peacefully?

Looking at the error message from your previous post, it’s the count on line 85 which is of interest. @Falco’s suggestion for editing the script is to increase that count to ignore some number of failures. The simplest way to achieve that is by entering the container and using sed to make an in-place substitution on that specific line. cd /var/discourse ./launcher enter app sed -i '85s/0/100/' lib/file_store/to_s3_migration.rb Run the rake task again after that and it will ignore up to 100 “post not remapped to new S3 upload URL” errors. The change will disappear the next time you rebuild. For the error message in the original post, line 77 is the one of interest as @Falco referenced. Just replace the line number in the sed command: sed -i '77s/0/100/' lib/file_store/to_s3_migration.rb

Something else you could try after having removed the file and completed the migration (and having downloaded the failing file) is to edit the post again to put the file back in. It’d be interesting to know if it fails to upload to S3 entirely or only during the migration task.

I got the same error, on 64 post. Impossible to find them on 80K files… What would happen if I delete local files (most of them are alredy migrated)?

I confirm that files are migrated, but I got the same error.

Any suggestions? Uploads are on s3 and work fine, but the task: migrate to s3 fails.

[image] Saiano: I got the same error, on 64 post. Impossible to find them on 80K files If you are okay with losing those 64 files, what I did when this same rake task kept failing on me is to edit it, and make it error inly if there are 100 errors instead of 1.

[image] Falco: f you are okay with losing those 64 files, what I did when this same rake task kept failing on me is to edit it, and make it error inly if there are 100 errors instead of 1. It would be fine for me. What Shoud I do to edit the task?

You can first try to run it with: SKIP_FAILED=1 rake uploads:migrate_to_s3. If that doesn’t work edit this line here and try again lib/file_store/to_s3_migration.rb main base_url = File.join(SiteSetting.Upload.s3_base_url, prefix) count = Upload.by_users.where("url NOT LIKE '#{base_url}%'").count if count > 0 error_message = "#{count} of #{Upload.count} uploads are not migrated to S3. #{failure_message}" raise_or_log(error_message, should_raise) success = false end cdn_path = SiteSetting.cdn_path("/uploads/#{@current_db}/original").sub(/https?:/, "") count = Post.where("cooked LIKE '%#{cdn_path}%'").count if count > 0 error_message = "#{count} posts are not remapped to new S3 upload URL. #{failure_message}" raise_or_log(error_message, should_raise) success = false end unless Rake::Task.task_defined?(MISSING_UPLOADS_RAKE_TASK_NAME) Discourse::Application.load_tasks end

Tried with SKIP_FAILED=100 rake uploads:migrate_to_s3 => 0 files Listing S3 files … .. => 81070 files Syncing files to S3 Updating the URLs in the database… Removing old optimized images… Flagging all posts containing lightboxes for rebake… 54453 posts were flagged for a rebake 53 posts are not remapped to new S3 upload URL. S3 migration failed for db ‘default’. I didn’t understand how to put the modified file on my discourse script

[image] Saiano: Tried with SKIP_FAILED=100 rake uploads:migrate_to_s3 I may have misunderstood, but I think you need to run SKIP_FAILED=1 to turn the SKIP_FAILED on, rather than assign an amount.

[image] Saiano: SKIP_FAILED=1 rake uploads:migrate_to_s3 Tried with this command. … same Result

Migrate_to_s3 fails

Product Support Self-hosting

Saiano (Saiano) February 21, 2022, 5:16pm 28

DONE! WONDERFUL Thank you!!

Topic		Replies	Views
1 of 16551 uploads are not migrated to S3. S3 migration failed for db 'default' Self-hosting cdn , s3	21	2094	July 11, 2023
Uploads migration to S3 fails Product Support	26	3676	May 7, 2021
Migrating old uploads to S3 Self-hosting s3	8	1774	May 11, 2021
Rake uploads:migrate_from_s3 fails Self-hosting s3	31	3622	April 24, 2021
Rake migrate_to_s3 errors Self-hosting s3	3	846	February 4, 2020

Migrate_to_s3 fails

Related topics