linkerd2: continues error with message tcp forward duplex error: Transport endpoint is not connected (os error 107)
we are receiving this error continually, I searched but did not find any solutions
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42640} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42068} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42652} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42050} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42074} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42212} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42156} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42280} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42230} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42380} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42364} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42320} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42276} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42414} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
E INFO proxy={server=out listen=127.0.0.1:4140 remote=10.44.2.3:42332} linkerd2_proxy::proxy::tcp forward duplex error: Transport endpoint is not connected (os error 107)
version info
Client version: stable-2.1.0
Server version: stable-2.1.0
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:54:59Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.4-gke.12", GitCommit:"d48a38d6599484b4b98c39d1c584a3662a67d486", GitTreeState:"clean", BuildDate:"2018-12-07T00:26:53Z", GoVersion:"go1.10.3b4", Compiler:"gc", Platform:"linux/amd64"}
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 17 (8 by maintainers)
We continually see this, especially when downloading large files into the container that is in the mesh from S3. For example pulling in a 3GB file will trigger the message multiple times until the download finishes. The download does finish successfully however. I’m guessing the S3 client is intelligent enough to do retries through the AWS SDK.