Skip to content
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

prometheus can not bind ip v4 address #2310

Closed
pc10201 opened this Issue Dec 30, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@pc10201
Copy link

pc10201 commented Dec 30, 2016

What did you do?

./prometheus -web.listen-address "0.0.0.0:9091"
./prometheus -web.listen-address ":9091"

What did you expect to see?

I want bind 0.0.0.0 let everyone can see the web.

What did you see instead? Under which circumstances?

 ss -lntup
Netid  State      Recv-Q Send-Q Local Address:Port               Peer Address:Port            
tcp    LISTEN     0      128              *:22                           *:*                   users:(("sshd",pid=1165,fd=3))
tcp    LISTEN     0      128             :::22                          :::*                   users:(("sshd",pid=1165,fd=4))
tcp    LISTEN     0      128             :::9091                        :::*                   users:(("prometheus",pid=9266,fd=21))

Environment

  • System information:
    CentOS 7 x64
    Linux 3.10.0-327.36.3.el7.x86_64 x86_64

  • Prometheus version:

./prometheus -version
prometheus, version 1.4.1 (branch: master, revision: 2a89e8733f240d3cd57a6520b52c36ac4744ce12)
  build user:       root@e685d23d8809
  build date:       20161128-09:59:22
  go version:       go1.7.3
@juliusv

This comment has been minimized.

Copy link
Member

juliusv commented Dec 31, 2016

The ss output doesn't indicate that Prometheus is not listening on v4, even if it just shows a v6 entry. When I run Prometheus in the same way, I get the same ss output, but I can still reach Prometheus on the v4 address. Does that not work for you?

@pc10201

This comment has been minimized.

Copy link
Author

pc10201 commented Jan 5, 2017

I am sorry.It is OK now.
Because centos firewalld service is active.So I stop it.

@pc10201 pc10201 closed this Jan 5, 2017

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 24, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.