-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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 Output causes panic on SIGHUP #1530
Comments
This is has been fixed already in 1.0.0-beta3: #1339 |
I'm still getting similar (but for
|
slightly different issue but I'll just reopen this one |
sparrc
added a commit
that referenced
this issue
Sep 12, 2016
sparrc
added a commit
that referenced
this issue
Sep 12, 2016
jackzampolin
pushed a commit
that referenced
this issue
Oct 7, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
When using prometheus output, a SIGHUP will cause process to panic and crash.
Relevant telegraf.conf:
System info:
Steps to reproduce:
Expected behavior:
Config reloads gracefully
Actual behavior:
Panic with:
Additional info:
I guess this is due to the configuration (default in our case) for the prometheus metrics endpoint not being freed from the http HandlerMux and the code blindly trying to reregister it again.
The text was updated successfully, but these errors were encountered: