S3::Error::RequestTimeout: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. about s3 HOT 7 OPEN

I'm sorry for the delay. I'm quite busy recently, so I'm afraid you need to debug the code on your own. You can also consider switching to a different S3 library.

from s3.

Hi, I had the same problem I will try to debug it but for me solution was:

File.open("file.png", :encoding => "BINARY")

Binary is the key.
If I will find out solution You could find it in my fork.

edit

Is really weird because right now it works even without binary attribute. Something strange going on.

from s3.

Thanks for reporting, please create a pull request when you fix the problem.

from s3.

For anyone trying to figure this out, use File.read instead of File.open or open

from s3.

@abunsenonesale Do you know how to reproduce this error?
Could you also provide explanation for that why read is better then open in this case?

I could not reproduce that error so I do not know if it was related with some specific ruby version or some other black magic.
If you could provide some details it will be cool to understand what happened and to fix that.

from s3.

I have this now, although it was working when I initially implemented it, it now doesn't!

require "s3"

service = S3::Service.new(
  :access_key_id     => ENV['ACCESS_KEY_ID'],
  :secret_access_key => ENV['SECRET_ACCESS_KEY']
)

bucket_name = ENV['BUCKET_NAME']
file = ENV['FILENAME']

bucket = service.buckets.find(bucket_name)

object = bucket.objects.build(file)
object.content = open(file)
object.save

Result

S3::Error::RequestTimeout: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.
from /Users/ian/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/s3-0.3.23/lib/s3/connection.rb:216:in `handle_response'

Using : ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin14]

[13] pry(main)> object.content = File.open("/Users/ian/Desktop/test.png")
=> #<File:/Users/ian/Desktop/test.png>

from s3.

Reading over here aws/aws-sdk-js#281 it seems it's an issue with the content-length.

from s3.