-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
addrConn.createTransport failed to connect to {Addr: "localhost:4317", ServerName: "localhost:4317", }. Err: connection error: desc = "transport: Error while dialing: dial tcp [::1]:4317: connect: connection refused" {"grpc_log": true} #11630
Comments
Hi, |
2024-11-08 16:25:28 2024-11-08T15:25:[email protected]/service.go:166Setting up own telemetry... |
The error you are seeing "tls: first record does not look like a TLS handshake" generally happens when something is attempting to call out using TLS and the other side isn't using TLS. Without seeing your full config.yaml, it's hard to give more advice, but I'd careful examine your yaml as the "insecure: true" seems right but doesn't seem to be set for the given log. |
any clue why are we getting this error? |
Describe the bug
Getting this error in opentelemetry collector container log
addrConn.createTransport failed to connect to {Addr: "localhost:4317", ServerName: "localhost:4317", }. Err: connection error: desc = "transport: Error while dialing: dial tcp [::1]:4317: connect: connection refused" {"grpc_log": true}
Steps to reproduce
I followed this URL
kubectl apply -f https://raw.githubusercontent.com/open-telemetry/opentelemetry-collector/v0.113.0/examples/k8s/otel-config.yaml
What did you expect to see?
I expect, opentelmenty receives traces and export to jeager
What did you see instead?
I see the error
addrConn.createTransport failed to connect to {Addr: "localhost:4317", ServerName: "localhost:4317", }. Err: connection error: desc = "transport: Error while dialing: dial tcp [::1]:4317: connect: connection refused" {"grpc_log": true}
What version did you use?
otel/opentelemetry-collector:latest
What config did you use?
Followed this
https://opentelemetry.io/blog/2023/jaeger-exporter-collector-migration/
exporters:
otlp:
endpoint: "http://localhost:4317" # Replace with a real endpoint.
tls:
insecure: true
Environment
local docker desktop
Additional context
The text was updated successfully, but these errors were encountered: