-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Needs RFC1918 Private Address or --cluster.advertise-address flag to start alertmanager #1434
Comments
@skorpy2009 Thanks for reporting this issue. Would you mind adding more details to "I added 192.168.2.2/24 to any of my interfaces"? It is surprising to me, that your system can not find its IP address or determine one. |
I guess OP's server just has public IP addresses |
@skorpy2009 can you share the IP addresses (eg It is indeed undocumented that you need to specify the |
|
Thanks! This is helpful. I'll fix the logic of |
Alertmanager fails to start when the memberlist library cannot find any private IP addresses on the system. This is a safeguard to avoid exposing cluster ports over the internet unintentionally. The workaround is to pass the --cluster.advertise-address argument to AlertManager. See also: prometheus/alertmanager#1437 prometheus/alertmanager#1434
Alertmanager fails to start when the memberlist library cannot find any private IP addresses on the system. This is a safeguard to avoid exposing cluster ports over the internet unintentionally. The workaround is to pass the --cluster.advertise-address argument to AlertManager. See also: prometheus/alertmanager#1437 prometheus/alertmanager#1434
What did you do?
Try to start the alertmanager. I used
/opt/alertmanager-0.15.0.linux-amd64/alertmanager --config.file /etc/prometheus/alertmanager.yml
What did you expect to see?
See the alertmanager start.
What did you see instead? Under which circumstances?
Alertmanager did not start. It started when I added
192.168.2.2/24
to any of my interfaces or when I added the--cluster.advertise-address
flag.It seems like it has something to do with: https://github.com/hashicorp/memberlist/blob/022f081/net_transport.go#L144
Environment
System information:
Linux 4.16.0-0.bpo.2-amd64 x86_64
Alertmanager version:
The text was updated successfully, but these errors were encountered: