-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Mac + Spring Boot 3.0: Connection Reset by Peer #33911
Comments
I'm getting the same issue with otel/opentelemetry-collector-contrib version 0.105.0 (Image ID: d85af9079167) If I run it as-is with default values, it works as expected. I can successfully send traces & see it appear in the collector's stdout. I'm also able to connect to the zPages extension through my browser. As soon as I try to start it up through a docker-compose file and use a custom configuration, even the ones from the documentation, I get the same startup logs, with no indication of any error, but any attempt to reach the collector results in error: Connection reset by peer |
We were having a similar
After that, we were able to connect without the reset error. This was with the That said, this output in the collector logs is probably relevant and may mean you'll want to take a different course than above:
We're just starting with OTel, so changing the endpoint for testing was most expedient. |
Hi there, I'm not using a Mac, but Ubuntu 22.04 on a Dell with an Intel Core i7, and I had the exact same issue when using docker-compose: The collector refused connections unless the IP address was explicitly set. |
I'm also having same issue with both otel-collector and otel-collector-contrib under docker container it doesn't matter if you use 0.0.0.0 or localhost or docker container ip, application can not talk to otel-collector . In my case I'm using otel java agent. otel-collector | 2024-09-05T20:31:49.646Z info localhostgate/featuregate.go:63 The default endpoints for all servers in components have changed to use localhost instead of 0.0.0.0. Disable the feature gate to temporarily revert to the previous default. {"feature gate ID": "component.UseLocalHostAsDefaultHost"} |
Component(s)
No response
What happened?
Description
I cannot, under any circumstance, talk to any of the endpoints or ports within the otel-collector, I'm always getting connection reset by peer. I've tried to walk the image back a few months and I'm still getting the same issue. The logs are completely empty. When I curl I always get connection reset by peer as well. I can't ssh into the container because I think it's a go container.
I think I'm doing something wrong, and that maybe this could be a point to improve docs.
I am using the latest imagine for the otel-collector-contrib with the following docker compose:
Steps to Reproduce
docker-compose-up
send any trace via any application to the open gRPC or http ports or try to connect via browser or curl any of the 43175, or 43185 or 55679.
Expected Result
Any http response from the server
Actual Result
Connection reset by peer
Collector version
6c936660d90b2e15307a63761a2ee9333bd39ac419d45f67fd5d30d5ea9ac267, 0.101.0, 0.103.1
Environment information
Environment
OS: MacOs 13.4.1 (c) on an M2 Pro chip
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: