-
Notifications
You must be signed in to change notification settings - Fork 228
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
After chaning S3_PATH backups fail with header mismatch #833
Comments
is rollback
Could you share the following commands result, Without sensitive data?
|
Putting it back doesn't fix it. I even blew away all the contents of that S3 bucket.
|
I'm experiencing the same error during upload to MinIO. I updated from clickhouse-backup version 2.3.0 to 2.4.30 and the upload stopped working. If I revert back to 2.3.0, everything works again. Here's my config and version:
|
Is your provider
|
something wrong with your lets remove anything from s3:
access_key: hidden_key
secret_key: hidden_key
bucket: tpl-ch-backups
endpoint: https://s3.example.com
force_path_style: true
path: clickhouse if error the same, please share logs with S3_DEBUG=1 |
with this config error the same
I only use MinIO. Debug Log
|
I see
in logs could you try to connect to minio directly without nginx in the middle? |
which minio version do you use? |
I'm using it in Kubernetes and this is the ENV variables set for the backup pod
Debug output:
minio version: 2023-04-28T18:11:17Z |
Yes, everything works perfectly on the altinity/clickhouse-backup:2.4.29 version. |
Confirmed 2.4.29 works for us too |
@tman5 @warhaus-kc please confirm, is 2.4.31 works good for you? |
2.4.31 works for me |
Confirmed works for me too. Thanks! |
Looks like related minio/minio#17662 |
After changing the
S3_PATH
variable frombackups/shard-{shard}
tobackups/ourapp/environment/shard-{shard}
backups are now failing:The text was updated successfully, but these errors were encountered: