Replies: 2 comments
-
@mephmanx, so sorry I missed this! Let me ask the silly question first: which version of Linkerd is this? We've made a bunch of changes in this recently so I want to make sure I'm looking at the right stuff. |
Beta Was this translation helpful? Give feedback.
0 replies
-
this is the version I am trying to use
My entire platform build is open source here |
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.
-
Im having issues with my linkerd / jaeger install. I am following the guides online and everything installs but the proxy sidecars keep throwing this error /warning.
[ 0.004040s] INFO ThreadId(01) linkerd2_proxy: release 2.308.0 (a6e47d7) by linkerd on 2025-07-15T17:58:06Z
[ 0.009288s] INFO ThreadId(01) linkerd2_proxy::rt: Using single-threaded proxy runtime
[ 0.011521s] INFO ThreadId(01) linkerd2_proxy: Admin interface on 0.0.0.0:4191
[ 0.011557s] INFO ThreadId(01) linkerd2_proxy: Inbound interface on 0.0.0.0:4143
[ 0.011567s] INFO ThreadId(01) linkerd2_proxy: Outbound interface on 127.0.0.1:4140
[ 0.011573s] INFO ThreadId(01) linkerd2_proxy: Tap interface on 0.0.0.0:4190
[ 0.011580s] INFO ThreadId(01) linkerd2_proxy: SNI is default.examples.serviceaccount.identity.linkerd.cluster.local
[ 0.011585s] INFO ThreadId(01) linkerd2_proxy: Local identity is default.examples.serviceaccount.identity.linkerd.cluster.local
[ 0.011591s] INFO ThreadId(01) linkerd2_proxy: Destinations resolved via linkerd-dst-headless.linkerd.svc.cluster.local:8086 (linkerd-destination.linkerd.serviceaccount.identity.linkerd.cluster.local)
[ 0.011596s] INFO ThreadId(01) linkerd2_proxy: Tracing collector at collector.linkerd-jaeger:4317 (collector.linkerd-jaeger.serviceaccount.identity.linkerd.cluster.local)
[ 0.014071s] INFO ThreadId(01) policy:controller{addr=linkerd-policy.linkerd.svc.cluster.local:8090}: linkerd_pool_p2c: Adding endpoint addr=10.42.0.35:8090
[ 0.014713s] INFO ThreadId(01) dst:controller{addr=linkerd-dst-headless.linkerd.svc.cluster.local:8086}: linkerd_pool_p2c: Adding endpoint addr=10.42.0.35:8086
[ 0.014732s] INFO ThreadId(02) identity:identity{server.addr=linkerd-identity-headless.linkerd.svc.cluster.local:8080}:controller{addr=linkerd-identity-headless.linkerd.svc.cluster.local:8080}: linkerd_pool_p2c: Adding endpoint addr=10.42.0.34:8080
[ 0.021230s] INFO ThreadId(01) tracing:controller{addr=collector.linkerd-jaeger:4317}: linkerd_pool_p2c: Adding endpoint addr=10.43.161.169:4317
[ 0.023854s] WARN ThreadId(01) tracing:controller{addr=collector.linkerd-jaeger:4317}:endpoint{addr=10.43.161.169:4317}: linkerd_reconnect: Failed to connect error=endpoint 10.43.161.169:4317: received corrupt message of type InvalidContentType error.sources=[received corrupt message of type InvalidContentType]
[ 0.024736s] INFO ThreadId(02) daemon:identity: linkerd_app: Certified identity id=default.examples.serviceaccount.identity.linkerd.cluster.local
[ 0.130674s] WARN ThreadId(01) tracing:controller{addr=collector.linkerd-jaeger:4317}:endpoint{addr=10.43.161.169:4317}: linkerd_reconnect: Failed to connect error=endpoint 10.43.161.169:4317: received corrupt message of type InvalidContentType error.sources=[received corrupt message of type InvalidContentType]
[ 0.353973s] WARN ThreadId(01) tracing:controller{addr=collector.linkerd-jaeger:4317}:endpoint{addr=10.43.161.169:4317}: linkerd_reconnect: Failed to connect error=endpoint 10.43.161.169:4317: received corrupt message of type InvalidContentType error.sources=[received corrupt message of type InvalidContentType]
[ 0.761195s] WARN ThreadId(01) tracing:controller{addr=collector.linkerd-jaeger:4317}:endpoint{addr=10.43.161.169:4317}: linkerd_reconnect: Failed to connect error=endpoint 10.43.161.169:4317: received corrupt message of type InvalidContentType error.sources=[received corrupt message of type InvalidContentType]
Here is my install process / script
Confirm version matches
[7:46 PM] Chris
my linkerd jaeger check looks good
ubuntu@srvr-node:~$ sudo linkerd jaeger check --kubeconfig /etc/rancher/rke2/rke2.yaml
linkerd-jaeger
√ linkerd-jaeger extension Namespace exists
‼️ jaeger extension pods are injected
‼️ jaeger injector pods are running
could not find proxy container for collector-75568c7c6f-b5t28 pod
see https://linkerd.io/2/checks/#l5d-jaeger-pods-injection for hints
container "linkerd-proxy" in pod "collector-75568c7c6f-b5t28" is not ready
see https://linkerd.io/2/checks/#l5d-jaeger-pods-running for hints
√ jaeger extension proxies are healthy
√ jaeger extension proxies are up-to-date
√ jaeger extension proxies and cli versions match
Status check results are √
ubuntu@srvr-node:~$
Beta Was this translation helpful? Give feedback.
All reactions