OTLP collector in 1.59.0 only listens on localhost instead of 0.0.0.0?

[famod]

Hi all,

when updating from 1.58.1 to 1.59.0 I noticed that my trace sending services based on Quarkus were suddenly throwing errors like: Connection refused: jaeger-tracing/172.18.0.9:4318
(this is inside a docker compose setup using jaegertracing-all-in-one).
I then realized that the collector in 1.59.0 is only listening on localhost instead of 0.0.0.0 (like in 1.58.1).

I was able to fix that via COLLECTOR_OTLP_HTTP_HOST_PORT=0.0.0.0:4318.

Question is: Is this to be expected? Is this issue caused by #5698?

Thanks!

[dosubot[bot]]

Hello @famod👋, I'm here to help you with any issues you're experiencing. I can assist with bug resolutions, answer questions, and guide you to become a contributor.

The issue you're experiencing with the OTLP collector in Jaeger 1.59.0 listening on localhost instead of 0.0.0.0 is not explicitly documented in the provided sources. However, you can resolve this by setting the COLLECTOR_OTLP_HTTP_HOST_PORT environment variable to 0.0.0.0:4318, as you have already done.

The default network binding settings for the Jaeger collector include various ports, but there is no specific mention of changes to the default binding behavior in the 1.59.0 release in the available documentation ^[1].

If you need further details, you might want to review the release notes or changelog for Jaeger 1.59.0, or check for any updates in the Jaeger repository that might provide more context.

To continue talking to Dosu, mention @dosu.

[yurishkuro]

This is a change introduced by receivers we use from OTEL collector. We have a fix in the next release #5739

[famod]

Thanks!

[gustaveWPM]

Hello @yurishkuro !
Using jaegertracing/all-in-one, I still have this issue.

https://hub.docker.com/r/jaegertracing/all-in-one/tags

I tried to use 1.59.0 and 1.59, and still experiment the same problem.
Using "latest", or 1.58, reverts it to normal.

I don't really understand what to do? ^^'
What is the fixed tag?

Minimal reproduction available here: https://github.com/gustaveWPM/prisma-with-open-telemetry

[yurishkuro]

the fix will be released in 1.60 (you can use latest now, or better a specific hash that latest points to)

[gustaveWPM]

the fix will be released in 1.60 (you can use latest now, or better a specific hash that latest points to)

Thank you a lot! :)