-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
Investigate spurious target-manager exit after startup #374
Comments
ghost
assigned juliusv
Jan 23, 2014
Found out that this was due to a panic happening, which triggered the deferred
|
This was triggered by two bugs:
|
juliusv
added a commit
that referenced
this issue
Jan 24, 2014
This fixes bug 2. of #374 Change-Id: Ia4a13153616bafce5bf10597966b071434422d09
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
Add cachebusting fingerprints to asset files.
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Prometheus was restarted and stopped scraping soon after startup. The relevent log section said:
After that, the web interface worked, but since scrapers (target pools) were down, returned no fresh data for any query.
Possibly (and maybe due to the long shutdown time before) there was an issue where Prometheus got another SIGTERM/SIGINT from its supervisor. But why did it not shut down completely then? The same happened for a group of Prometheus instances at the same time, when they each got a new target configured. After another restart, everything is working.
The text was updated successfully, but these errors were encountered: