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.

Sign up for GitHub

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

Jump to bottom

Amazon S3 errors since upgrade from 3.3.9 to 3.5.1 #213

Open
brianamos1 opened this issue Mar 19, 2023 · 12 comments
Open

Amazon S3 errors since upgrade from 3.3.9 to 3.5.1 #213

brianamos1 opened this issue Mar 19, 2023 · 12 comments

Comments

@brianamos1
Copy link

I started getting the following error after upgrading my server os, which included upgrading from Amanda 3.3.9 to 3.5.1. After the error I uninstalled 3.5.1 and built 3.5.2 from source. I continue getting the same error. The error says:

While writing amanda header: The request signature we calculated does not match the signature you provided. Check your key and signing method. (SignatureDoesNotMatch) (HTTP 403).

I have checked my access key and secret key, and they are correct. I tried using new keys (on both root account and and that also didn't make any difference. I've tried changing the device properties to various different settings with no luck. I've even tried starting a new backup, both from scratch and from the S3 template. I updated my device definition per the man page and that hasn't worked either. Has anyone seen this issue? Or have any advice ?

All of my searching on google doesn't turn anything up, and with the zmanda forums down, I don't know where go to but here. I've skimmed the code and gone through the s3 files, but with no familiarity with this code base, I don't know where to look for the issue. I am wondering if it's an issue with curl or some other library that is the culprit and not amanda. I'm just looking if anyone has experience this or has any direction where I can look to fix this.
@brianamos1
Copy link
Author

I can report that this is not an issue with the 3_6 branch, but it is an issue with the main branch.

@hubandr
Copy link

hubandr commented Mar 20, 2023

had the same problem a few weeks ago. Downgrading of the latest curl security fixes solved the problem (for now).

On Debian 10:
apt install libcurl4=7.64.0-4+deb10u2 curl=7.64.0-4+deb10u2

@Gouagou
Copy link

Gouagou commented Mar 31, 2023

Same problem on Debian 11.6
Downgrading solve the problem:
apt install libcurl4=7.74.0-1.3+deb11u3 curl=7.74.0-1.3+deb11u3

@stefangweichinger stefangweichinger mentioned this issue Mar 31, 2023
Open
@shrodi
Copy link

shrodi commented Apr 19, 2023

Same problem on Ubuntu 22.04 LTS.

Downgrading libcurl4 from 7.81.0-1ubuntu1.10 to 7.81.0-1 solved the problem for me:
apt install libcurl4=7.81.0-1

I put the package on hold for now:
apt-mark hold libcurl4

@jamshid jamshid mentioned this issue May 26, 2023
Merged
@stefangweichinger
Copy link
Contributor

Same problem on Debian 11.6 Downgrading solve the problem: apt install libcurl4=7.74.0-1.3+deb11u3 curl=7.74.0-1.3+deb11u3

"...deb11u7" for Debian 11.7 in the meantime

Unfortunately this doesn't fix things for me right now.

slot 1: Can't read label: While trying to read tapestart header: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method. (SignatureDoesNotMatch) (HTTP 403)

@brianamos1
Copy link
Author

brianamos1 commented Jun 2, 2023 via email

@chassell
Copy link

chassell commented Jun 3, 2023 via email

@stefangweichinger
Copy link
Contributor

Google wasn't working well and they've changed their protocol several times. It needs work.

@chassell thanks for that short bit. Sounds as if I have to look for something else.

@stefangweichinger
Copy link
Contributor

Google wasn't working well and they've changed their protocol several times. It needs work.

@chassell Does that mean that also 3_6 can not be trusted with the S3 device currently? Could you explain in more detail what does not work well? I invested lots of time in trying to make this work here and have to decide how to proceed. Thanks.

@Gouagou
Copy link

Gouagou commented Jun 5, 2023 via email

@stefangweichinger
Copy link
Contributor

I have equally try the 3.6.0.pre3+1 version, amdump is working. But amrecover failed, only the folders are restored . And the job never finished...

ouch! Backups without Restore aren't worth much ...

@superwooman
Copy link

had the same problem a few weeks ago. Downgrading of the latest curl security fixes solved the problem (for now).

On Debian 10: apt install libcurl4=7.64.0-4+deb10u2 curl=7.64.0-4+deb10u2

Same here. Tried many other things but this solution works. Thanks

@prajwaltr93 prajwaltr93 mentioned this issue Dec 10, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@Gouagou @stefangweichinger @hubandr @brianamos1 @shrodi @chassell @superwooman