Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upInvestigate spurious target-manager exit after startup #374
Comments
ghost
assigned
juliusv
Jan 23, 2014
This comment has been minimized.
This comment has been minimized.
|
Found out that this was due to a panic happening, which triggered the deferred
|
This comment has been minimized.
This comment has been minimized.
|
This was triggered by two bugs:
|
juliusv
added a commit
that referenced
this issue
Jan 24, 2014
juliusv
closed this
Mar 9, 2014
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 25, 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
bot
locked and limited conversation to collaborators
Mar 25, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
juliusv commentedJan 23, 2014
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.