Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wasabi S3 Errors #1064

Open
r1chjames opened this issue Feb 3, 2025 · 2 comments
Open

Wasabi S3 Errors #1064

r1chjames opened this issue Feb 3, 2025 · 2 comments

Comments

@r1chjames
Copy link

r1chjames commented Feb 3, 2025

I've been using Wasabi S3-compatible storage using CNPG, however recently my backups have been failing with the following error:
failure uploading data (An error occurred (InvalidRequest) when calling the UploadPart operation: Checksum Type mismatch occurred, expected checksum Type: null, actual checksum Type: crc32).

I can't pinpoint when it stopped working, however I'm running with the following config:

backup:
    barmanObjectStore:
      destinationPath: 's3://[REDACTED]-cnpg-backups/shared'
      endpointURL: 'https://s3.eu-west-1.wasabisys.com'
      s3Credentials:
        accessKeyId:
          name: wasabi-secret
          key: ACCESS_KEY_ID
        secretAccessKey:
          name: wasabi-secret
          key: ACCESS_SECRET_KEY

I'm unsure whether it's related to the change to 3.12, just wondering if anyone else had seen something similar. I've moved to AWS S3 and it works so presumably it's a specific issue in the Wasabi implementation of S3 API.

@f-prime
Copy link

f-prime commented Feb 5, 2025

I had the same issue (unrelated to barman). It started happening when I upgraded to boto3 1.36.13. After I downgraded to 1.35.19 the issues were resolved.

I am not sure of what is causing this exactly though.

@martinmarques
Copy link
Contributor

@f-prime Boto3 1.36 introduced a breaking change. That's why in Barman we are pinning 1.35.99 to our Barman builds until we provide the needed changes for 1.36.x to work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants