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 upService discovery Azure [Error discovery manager] #4325
Comments
This comment has been minimized.
This comment has been minimized.
|
I'd say that your Prometheus service has hit the file descriptor limits. See https://github.com/prometheus/prometheus/wiki/FAQ#error-too-many-files-open for more details. I'm going to close your request. If you need more help, please use the prometheus-users mailing list. |
simonpasquier
closed this
Jul 4, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 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 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
ghost commentedJun 29, 2018
Bug Report
What did you do?
I configured Service discover Azure and it worked during 1 months without problems but I got a strange error last night. See logs below.
What did you expect to see?
Should discovery VM without problems. I just restarted Prometheus to solve the problem but it appears again last night.
What did you see instead? Under which circumstances?
Logs error from discovery manager
Environment
System information:
Linux 4.15.0-1013-azure x86_64
Prometheus version:
version 2.2.0
Logs: