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 On Wednesday, August 5, 2020 at 6:23:03 AM UTC-4, Christian Hoffmann wrote: > > 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 > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/abfaacea-01af-4c80-94fd-57590164ddfeo%40googlegroups.com.
