Seeing many errors during cron exeuction, "Your socket connection to the server was not read from or written to within the timeout period." [#2659272]

I have many files waiting in local storage that need to be moved to S3. When I run the cron via drush, I get a screen full of:

WD storage_s3: Amazon S3 error: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. [error]

There are no additional errors in the error log. Watchdog just reports the same error.

I see some images in my s3 bucket. But there are many more that are not there.

Comments

Comment #1

30 January 2016 at 01:07

royl-development created an issue. See original summary.

Comment #2

Perignon CreditAttribution: Perignon commented 30 January 2016 at 08:24

Can you give me steps to replicate?

Comment #3

royl-development CreditAttribution: royl-development commented 1 February 2016 at 19:28

Here is my workflow. It's basic content editing. Nothing out of the ordinary here.

Create new content, add images to image fields.
Execute `drush core-cron` from CLI
Watch errors roll in

On my local development machine there are no errors, same for my staging server. It only occurs on production. I am working with the IT company to rule out any network issues.

Wondering if I can just increase the timeout value? I do not see any such configuration available though.

Comment #4

Perignon CreditAttribution: Perignon commented 1 February 2016 at 20:25

Interesting. On your local or staging does the files move as they are supposed to?

Is your production environment a shared or dedicated hosting?

Comment #5

royl-development CreditAttribution: royl-development commented 1 February 2016 at 23:38

Yes, on local and staging the files more as they are supposed to.

Production is dedicated hosting.

I copied the prod DB to my local, rsynced all of the files from prod to local, and re-ran cron on my local dev site successfully. I am 100% sure this is a network issue on the production environment and there is nothing wrong with the module.