Skip to content

/prometheus

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

Panic when Consul SD can't be connected to #1233

Closed
brian-brazil opened this Issue Nov 22, 2015 · 3 comments

Comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@brian-brazil @wrouesnel @fabxc
@brian-brazil
Copy link
Member

brian-brazil commented Nov 22, 2015 

time="2015-11-22T17:37:16Z" level=info msg="Loading configuration file /etc/prometheus/prometheus.yml" source="main.go:196" 
panic: discovery.NewConsulDiscovery: Get http://127.0.0.1:8500/v1/agent/self: dial tcp 127.0.0.1:8500: getsockopt: connection refused

This shouldn't take out the Prometheus server.
@wrouesnel

This comment has been minimized.

Sign in to view
Copy link
Contributor

wrouesnel commented Nov 30, 2015

+1 just discovered this.

@fabxc fabxc closed this Nov 30, 2015

@fabxc

This comment has been minimized.

Sign in to view
Copy link
Member

fabxc commented Nov 30, 2015

Fixed by #1248
@lock

This comment has been minimized.

Sign in to view
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.