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

Issue with MultipartUpload since 3.31.0. Getting timeout response. #1326

Closed
graphem opened this issue Jul 10, 2017 · 8 comments
Closed

Issue with MultipartUpload since 3.31.0. Getting timeout response. #1326

graphem opened this issue Jul 10, 2017 · 8 comments
Labels
bug This issue is a bug.

Comments

@graphem
Copy link

graphem commented Jul 10, 2017

I am using the plugin https://github.com/spatie/laravel-backup to run upload to S3 using PUT method. Since 3.31.0 release, we are getting these errors from S3:

<?xml version="1.0" encoding="UTF-8"?> <Code>RequestTimeout</Code><Message>Your socket connection to the server w (truncated...) RequestTimeout (client): Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. - <?xml version="1.0" encoding="UTF-8"?> <Code>RequestTimeout</Code><Message>Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.</Message>

Seems to only occuring when doing MultipartUpload. Anyone else experiencing this issue with any other integration using this aws package? Thanks!

@dvlpp
Copy link

dvlpp commented Jul 10, 2017

I can confirm this issue. To be more specific, the spatie/laravel-backup package uses the well-known thephpleague/flysystem-aws-s3-v3 package under the hood, and the issue was also reported here: https://github.com/thephpleague/flysystem-aws-s3-v3/issues/113.

@abiturma
Copy link

I encountered the exact same problem.

@vkulov
Copy link

vkulov commented Jul 10, 2017

We are having the same issue. Had to downgrade to 3.30.4

@kstich
Copy link
Contributor

kstich commented Jul 10, 2017

Thanks everyone for bringing this to our attention. It looks like you end up with an internal MultipartUploader which is being passed a seekable stream, which is not setting the ContentLength on the part to the proper size. We will have a PR up shortly fixing this issue.

@kstich kstich added bug This issue is a bug. investigating This issue is being investigated and/or work is in progress to resolve the issue. labels Jul 10, 2017
@HSken
Copy link

HSken commented Jul 12, 2017

Same issue

@zlodes
Copy link

zlodes commented Jul 12, 2017

Same, last version, php 7.1.0

@kstich
Copy link
Contributor

kstich commented Jul 12, 2017

We believe this issue has been fixed as of version 3.31.3. Thank you again for the reports.

@graphem
Copy link
Author

graphem commented Jul 12, 2017

Confirmed, this is fixed. Thanks!!!!

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

No branches or pull requests

8 participants