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

alertmanager pod start failed #5359

Closed
weilinqwe opened this Issue Mar 14, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@weilinqwe
Copy link

weilinqwe commented Mar 14, 2019

Alertmanager version: v0.15.2

[root@cloudhost1 prometheus]# kubectl get pod   -n monitoring                                                  
NAME                                                     READY     STATUS             RESTARTS   AGE
grafana-796ffb9558-4d4fw                                 1/1       Running            0          17m
monitor-prometheus-alertmanager-67dd877d66-xxdlj         1/2       CrashLoopBackOff   1          18s
monitor-prometheus-kube-state-metrics-78b6c5f4d9-fk2k7   1/1       Running            0          18m
monitor-prometheus-node-exporter-brk52                   1/1       Running            0          18m
monitor-prometheus-node-exporter-h8dgb                   1/1       Running            0          18m
monitor-prometheus-node-exporter-mlx88                   1/1       Running            0          18m
monitor-prometheus-node-exporter-xgznb                   1/1       Running            0          18m
monitor-prometheus-node-exporter-zc2hq                   1/1       Running            0          18m
monitor-prometheus-server-8f44b6c7d-hdtl4                2/2       Running            0          18m

[root@cloudhost1 prometheus]# kubectl logs  monitor-prometheus-alertmanager-67dd877d66-xxdlj -c prometheus-alertmanager-configmap-reload -n monitoring
2019/03/14 12:18:18 Watching directory: "/etc/config"
[root@cloudhost1 prometheus]# kubectl logs  monitor-prometheus-alertmanager-67dd877d66-xxdlj -c prometheus-alertmanager -n monitoring
level=info ts=2019-03-14T12:19:58.378674034Z caller=main.go:174 msg="Starting Alertmanager" version="(version=0.15.2, branch=HEAD, revision=d19fae3bae451940b8470abb680cfdd59bfa7cfa)"
level=info ts=2019-03-14T12:19:58.378827621Z caller=main.go:175 build_context="(go=go1.10.3, user=root@3101e5b68a55, date=20180814-10:53:39)"
level=warn ts=2019-03-14T12:19:58.394107651Z caller=cluster.go:148 component=cluster err="couldn't deduce an advertise address: no private IP found, explicit advertise addr not provided"
level=error ts=2019-03-14T12:19:58.421706704Z caller=main.go:199 msg="unable to initialize gossip mesh" err="create memberlist: Failed to get final advertise address: No private IP address found, and explicit IP not provided"

Anyone can give a clue?

@simonpasquier

This comment has been minimized.

Copy link
Member

simonpasquier commented Mar 15, 2019

The pod has an IP address from a public Internet subnet and the memberlist library won't start unless you explicitly provide the address via the --cluster.advertise-address parameter. Assuming that the pod isn't effectively exposed directly to the Internet, you should be able to use the Downward API to pass the value to the container.

I'm closing it for now. If you have further questions, please use our user mailing list, which you can also search.

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