Fix this: rake aborted! AWS::S3::Errors::RequestTimeout: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.

Ok, I have been a couple of hours trying to find the solution to this:

rake aborted!
AWS::S3::Errors::RequestTimeout: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.

I was trying to run a rake:seed command in heroku

$ heroku run rake db:seed

And I got the above mentioned error once and again. It was strange because the behaviour was erratic, sometimes it would upload one file and break, and the next it could do the following.

Finally, I decided to investigate what was happening in the Amazon Bucket. So I opened the bucket and saw that there were some files. I then deleted all the folders with the contained files. And… magic! the error disapeared.

So what is my conclusion? there was something corrupt, or maybe you cannot run the seeds two times. Honestly, I have not tried a second time. It was already quite hard to get here. Next time I reset the database (it is in a staging app), I will find out if files in AWS S3 have to be deleted each time to avoid this conflict.

Hope this info is useful anyway! good luck

Advertisements

Changing ownership AWS Amazon S3 bucket

After some research, as of today, it is not easy to change one S3 bucket from one user to another. I have found this solution:

http://stackoverflow.com/questions/5518205/move-files-directly-from-one-s3-account-to-another

and this other one using a proprietary solution http://support.bucketexplorer.com/topic1165.html

But could not implement it, since I don’t understand well how the IAM works.

So I went for the simplest way: delete the original bucket and create a new one with the same name

Warning: you will have to wait to have the name released.

If you try to create a new bucket with the same name right after you delete it, you will receive the warning:

A conflicting conditional operation is currently in progress against this resource. Please try again.