Client-go: HTTP port-forward broke on client terminates
Situation
- Components are connected as Go server -> port-forward -> iOS Client
- Using chunked transfer encoding to download large movie file from Server to iOS
problem
When iOS client exits with SIGKILL (i.e. restart app from Xcode), the port forward emits an error
E1119 14:59:19.967004 9736 portforward.go:303] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:8888->127.0.0.1:35390: write tcp4 127.0.0.1:8888->127.0.0.1:35390: write: broken pipe
It is ok, but after this error, all connections to portforward are rejected with timeout.
E1119 15:15:07.167402 9736 portforward.go:271] error creating error stream for port 8888 -> 8888: Timeout occured
Expected behavior
portforward accepts the following requests after broken pipe.
tomykaira
All 29 comments
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 17 Feb 2018
/remove-lifecycle stale
I can confirm that this happens running with linux clients using curl. If the endpoint streams results back to the client, and the client (ie, curl) is terminated via ctrl-c, the port-forward does not respond to future requests until the timeout.
andrewshilliday
on 2 Mar 2018
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 31 May 2018
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale
fejta-bot
on 2 Jul 2018
/remove-lifecycle rotten
yonilerner
on 2 Jul 2018
@tomykaira are you still experiencing the same issues? I have the same problem
pedrocunha
on 24 Aug 2018
I definitely still happen. I basically just have to try over and over until it works once
yonilerner
on 24 Aug 2018
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 22 Nov 2018
/remove-lifecycle stale
yonilerner
on 22 Nov 2018
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 20 Feb 2019
/remove-lifecycle stale
yonilerner
on 20 Feb 2019
@yonilerner We had this issue as well on our build servers, though it was not intermittent for this particular port-forward -> curl. Turned out to be an expired cert. Might be worth double-checking.
s1dequest
on 25 Feb 2019
@s1dequest Thanks for the suggestion, but our certs are fine. port-forward always works, its just not stable
yonilerner
on 25 Feb 2019
Experience same error using Kubernetes in Azure when opening a tunnel to the cluster with az aks browse. Works for a time, then starts to get this error and the tunnel becomes very unstable.
paaland
on 1 Mar 2019
Can confirm the same on my AKS cluster on azure. The deployment / upgrade goes through and deployment is runned. But the Release pipeline is marked as failed.
4383 portforward.go:363] error copying from remote stream to local connection: readfrom tcp4 127.0.0.1:43163->127.0.0.1:56726: write tcp4 127.0.0.1:43163->127.0.0.1:56726: write: broken pipe
daniel-hirvonen
on 25 Mar 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 23 Jun 2019
/remove-lifecycle stale
yonilerner
on 24 Jun 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 22 Sep 2019
/remove-lifecycle stale
yonilerner
on 25 Sep 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 24 Dec 2019
/remove-lifecycle stale
yonilerner
on 24 Dec 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 23 Mar 2020
/remove-lifecycle stale
yonilerner
on 23 Mar 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 21 Jun 2020
/remove-lifecycle stale
yonilerner
on 21 Jun 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 19 Sep 2020
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
fejta-bot
on 20 Oct 2020
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
fejta-bot
on 19 Nov 2020
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
k8s-ci-robot
on 19 Nov 2020
Related issues
narasago
路
3Comments
inetkiller
路
6Comments
peterwillcn
路
5Comments
h0tbird
路
3Comments
prestonvanloon
路
6Comments
Most helpful comment
Experience same error using Kubernetes in Azure when opening a tunnel to the cluster with az aks browse. Works for a time, then starts to get this error and the tunnel becomes very unstable.