Can not access backup page and related error when restoring using GCP Object Storage

support
1

image
image788×201 9.22 KB

Hello I have setup backup to GCP Storage following the guide but a few day later when trying to access /admin/backups this error shows up. Additionally no backups was generated & uploaded to GCP until I manually trigger a backup from the UI. Then, when I attempt to restore the said backup on a new instance this error shows up:

Job exception: The XML you provided was not well-formed or did not validate against our published schema.
aws-sdk-core-3.109.2/lib/seahorse/client/plugins/raise_response_errors.rb:17:in `call'
aws-sdk-s3-1.83.2/lib/aws-sdk-s3/plugins/sse_cpk.rb:24:in `call'
aws-sdk-s3-1.83.2/lib/aws-sdk-s3/plugins/dualstack.rb:30:in `call'
aws-sdk-s3-1.83.2/lib/aws-sdk-s3/plugins/accelerate.rb:47:in `call'
aws-sdk-core-3.109.2/lib/aws-sdk-core/plugins/jsonvalue_converter.rb:22:in `call'
aws-sdk-core-3.109.2/lib/aws-sdk-core/plugins/idempotency_token.rb:19:in `call'
aws-sdk-core-3.109.2/lib/aws-sdk-core/plugins/param_converter.rb:26:in `call'
aws-sdk-core-3.109.2/lib/seahorse/client/plugins/request_callback.rb:71:in `call'
aws-sdk-core-3.109.2/lib/aws-sdk-core/plugins/response_paging.rb:12:in `call'
aws-sdk-core-3.109.2/lib/seahorse/client/plugins/response_target.rb:24:in `call'
aws-sdk-core-3.109.2/lib/seahorse/client/request.rb:72:in `send_request'
aws-sdk-s3-1.83.2/lib/aws-sdk-s3/client.rb:8959:in `put_bucket_lifecycle_configuration'
/var/www/discourse/lib/s3_helper.rb:176:in `update_lifecycle'
/var/www/discourse/lib/s3_helper.rb:186:in `update_tombstone_lifecycle'
/var/www/discourse/lib/file_store/s3_store.rb:142:in `purge_tombstone'
/var/www/discourse/app/jobs/scheduled/purge_deleted_uploads.rb:10:in `execute'
/var/www/discourse/app/jobs/base.rb:232:in `block (2 levels) in perform'
rails_multisite-2.5.0/lib/rails_multisite/connection_management.rb:76:in `with_connection'
/var/www/discourse/app/jobs/base.rb:221:in `block in perform'
/var/www/discourse/app/jobs/base.rb:217:in `each'
/var/www/discourse/app/jobs/base.rb:217:in `perform'
/var/www/discourse/app/jobs/base.rb:279:in `perform'
mini_scheduler-0.13.0/lib/mini_scheduler/manager.rb:93:in `process_queue'
mini_scheduler-0.13.0/lib/mini_scheduler/manager.rb:37:in `block (2 levels) in initialize'

The S3 integration seems to work since user images are upload and the manual triggered backup also…

2

Isn’t this s3 incompatibility @Falco

1 Like
3

Yes, GCP has the worse compatibility of all providers. We can’t read files, and to get assets in there we even have a special ENV variable so we are read-only.

@wollacsek nothing we can do since we implement the S3 calls and only GCP fails here. I will add a warning to Using Object Storage for Uploads (S3 & Clones)

3 Likes