Open Alan01252 opened 8 years ago
Are you behind a proxy?
Does setting sslEnabled: false
e.g. https://github.com/faceleg/node-s3-client/blob/97a90cdaaf73c359ce4efb969a0f5b1166ddffd8/test/test.js#L40 help?
Thank you for your reply! :)
We're not behind a proxy, code is running on a linode and directly talking to S3. I haven't tried running without SSL and I'm not sure that's a viable option for us.
It's a really intermittent problem, we're using the library a fair bit, and it's only occasionally crashing due to this. Perhaps once every few hours.
I suspect bumping the aws-sdk library might help.
Tried using your fork with updated aws-sdk that still didn't help! Will have to dedicate to look through this next week :)
For anyone else who comes across this, we seem to of solved this problem by increasing the allowed connection pool further.
http.globalAgent.maxSockets = https.globalAgent.maxSockets = 100;
Seems to be working for us now.
If you would update the readme with this tip I would be forever in your debt!
Hi,
We've been struggling with this today, not entirely sure why the connection was getting reset yet. I'm not entirely sure looking at the code where/how it would be best to catch this. Any help would be greatly appreciated. At the moment the error isn't caught and so it takes down the node application entirely.
Stack trace follows:
Thank you!
Alan