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

Broken Pipe Error Uploading #6587

Closed
cyberduck opened this issue Mar 14, 2012 · 4 comments
Closed

Broken Pipe Error Uploading #6587

cyberduck opened this issue Mar 14, 2012 · 4 comments
Assignees
Labels
bug duplicate high priority s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Mar 14, 2012

074f19e created the issue

While uploading to to my Amazon s3 account I keep getting a broken pipe error. I'm sure my Amazon cloud doesn't have a disk quota. I tried a different client and it's able to upload just fine for all types of files.

I prefer to use cyberduck for this. I can upload a 50mb file no problem but anything higher gives me a broken pipe error.


Attachments

@cyberduck
Copy link
Collaborator Author

cyberduck commented Mar 15, 2012

@dkocher commented

As this issue is only related to multipart uploads we have increased the threshold in 0b28636 effectively disabling multiparts for files smaller than 5GB.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 8, 2012

ed03e8c commented

I had the same "Broken pipe" problem when uploading files on S3
Plus other alert types "Socked closed" + "Skyped xxxxx bytes instead of yyyyy"

I installed the last snapshot build :
I still get a warning message at connexion :
S3 Erreur: S3 Error Message
S3 Error Message. Forbidden. Access Denied.
As usual I could get connected whatever button I click on (Cancel or Retry)

For the first time my upload (a 40Mo .mp4 file) could be achieved with Cyberduck...
I'll try with other uploads next week or even later (sorry) and I'll tell you if the problem reappears.

-Edit* :
2 days later I uploaded 2 files (170Mo + 30Mo) : OK  
So now the only problem is the warning message at connexion...

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jul 15, 2014

@dkocher commented

Duplicate for #7621.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jul 15, 2014

@dkocher commented

Duplicate for #7621. Fix in e1f5ff8 with Expect: 100-continue header for PUT requests that resolves broken pipe failures for uploads to buckets where a 307 Temporary Redirect is returned.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug duplicate high priority s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants