Able to specify bind port, but not address

[jumble]

Latest prometheus, on RHEL8.

Tried command: ./prometheus
Expected behavior: bind to 0.0.0.0:9090
Observed behavior: bound to 127.0.0.1:9090




Tried command: ./prometheus --web.listen-address=0.0.0.0:9090
Expected behavior: bind to 0.0.0.0:9090
Observed behavior: bound to 127.0.0.1:9090




Tried command: ./prometheus --web.listen-address=0.0.0.0:9000
Expected behavior: bind to 0.0.0.0:9000
Observed behavior: bound to 127.0.0.1:9000

[jumble]

"latest prometheus" -> prometheus-2.20.0.linux-amd64

[Christian Hoffmann]

Hi,

On 8/4/20 3:23 PM, jumble wrote:
> Latest prometheus, on RHEL8.

>
> Observed behavior: bound to |127.0.0.1:9090|

This sounds unexpected. Are you using the official binaries from
prometheus.io / github?

Can you share the exact logs from your experiments?

Is it possible that you've got multiple Prometheus installations, i.e.
one that is already running (bound to localhost) and the one where you
tried to run experiments?

I suggest checking the process list (ps aux | grep prometheus), watching
the logs for "address already in use" messages and/or trying a different
port.

It would be really surprising if this was a bug in Prometheus, Go or
RHEL8. But who knows :)

Kind regards,
Christian

[jumble]

Christian,

Thanks for your response! After a second look, the perceived bug was actually a combination of two non-Prometheus issues:

- Other firewall rules were preventing connections to port 9090.
- I misread netstat's output- Prometheus was binding to port 9090 for all IPv6 addresses and _implicitly_ binding in IPV4 (this binding isn't printed in netstat!)

Hope you and yours are well,

John