vapor: Resource temporarily unavailable after 30 seconds

Another socket issue that occurs after 30 seconds. It happens on Ubuntu 16.04 with Swift 3.0.1 and Vapor 1.1.10 on an EC2 instance running behind an Elastic Load Balancer:

Server error: dispatch(Transport.StreamError.receive("There was a problem while receiving data.", Socket failed with code 11 ("Resource temporarily unavailable") [readFailed] "Unknown error"))

Is it important or can we silence that error, too?

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 29 (7 by maintainers)

Most upvoted comments

Any chance we can get this reopened? I’m seeing this on an EC2 instance behind a load balancer

Server error: dispatch(Transport.StreamError.receive("There was a problem while receiving data.", Socket failed with code 11 ("Resource temporarily unavailable") [readFailed]))

Ubuntu 14.04 Swift 3.1 Vapor 1.5.15

vlaminck on Apr 11, 2017

Same error on DigitalOcean with Swift 3.1 and Vapor 1.5.15 under Ubuntu 16.04

acche on Apr 18, 2017

Same error follow doc getting-started guide -> hello-world Swift version 3.0.2 (swift-3.0.2-RELEASE) Vapor 1.5.9 Ubuntu 16.04

skymaze on Mar 10, 2017

v1.5.8 the same error shows 30 sec after each request. Running on (Digital Ocean) Ubuntu 16.04. Application is Hello World example from the documentation. screen shot 2017-03-05 at 00 03 07

cikabole on Mar 4, 2017

Try with Vapor 1.3.1. Just released: https://github.com/vapor/vapor/releases/tag/1.3.1

tanner0101 on Dec 16, 2016

@skreutzberger I’ll look into this one as well to see if we can narrow down the cause. My guess is that its the same thing.

loganwright on Nov 4, 2016