linkerd2_reconnect::service: Service failed error=channel closed #5306
Unanswered
RagingPuppies
asked this question in
General
Replies: 2 comments
-
@RagingPuppies Did you get an answer to this? I am also facing the same problem. and I have a feeling it's something to do with the actual grpc service and not linkerd2.. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This message indicates that the proxy lost its connection to the local application and is reconnecting. The message originates here: https://github.com/linkerd/linkerd2-proxy/blob/bffdb1aad8bb5479316a401de148a290b001dd44/linkerd/reconnect/src/lib.rs#L101-L118 Without more information it's not possible to know why the connection was closed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
i can see this error pops up on high load,
does it means that the linkerd-proxy disconnected from the serving container? what can be the root cause for that?
GRPC HTTP/2 connection..
i dont see any failures on the serving container... no restart or whatever..
[665928.951641986s] WARN inbound:accept{peer.addr=10.42.183.108:50520}:source{peer.id=Some("default.site-production.serviceaccount.identity.linkerd.cluster.local") target.addr=10.42.81.246:5000}:logical{dst=whatever-2020-10.site-production.svc.cluster.local:5000}:endpoint{peer.addr=10.42.81.246:5000}: linkerd2_reconnect::service: Service failed error=channel closed
Beta Was this translation helpful? Give feedback.
All reactions