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 upopen consoles/node.html: no such file or directory #1540
Comments
This comment has been minimized.
This comment has been minimized.
|
Hmm, it still works for me - what is your exact Prometheus command line? |
This comment has been minimized.
This comment has been minimized.
Might be a tailing slash missing.... P.S. But I would really love to see something like |
This comment has been minimized.
This comment has been minimized.
|
By default, Prometheus looks for your console files in the If it worked for you before, maybe it is because you still also had a For your path, you'll need to set |
brian-brazil
added
the
question
label
Apr 9, 2016
This comment has been minimized.
This comment has been minimized.
Nope, I've been running it with runit so nothing really changed except the prometheus version. Will try templates options now, thank you! |
hryamzik
closed this
Apr 9, 2016
This comment has been minimized.
This comment has been minimized.
|
@hryamzik That's odd - I can't really explain why it worked before then, unless the current working directory contained those dirs. Do runit-started services perhaps inherit the current working dir from the user who starts them (a common problem with some supervisor systems is also that env vars leak in from the user who starts/stops services, etc. - something which systemd fixes)? |
This comment has been minimized.
This comment has been minimized.
|
In fact I've also had to move from sudo to chpst on runit and that may be the cause. As we still run a lot of 14.04 I'm not going to change runit to systemd for now... |
This comment has been minimized.
This comment has been minimized.
kaihendry
commented
Jun 7, 2017
|
I think I have the same issue
Upon https://prom.dabase.com/consoles/node.html I'm launching prom/prometheus like so: https://github.com/kaihendry/pingprom/blob/master/prometheus%40.service |
This comment has been minimized.
This comment has been minimized.
|
Had the same issue as @kaihendry above, but was resolved by setting |
This comment has been minimized.
This comment has been minimized.
kaihendry
commented
Jul 19, 2017
|
Oh I forgot to mention I fixed it like so kaihendry/pingprom@395a4c6, i.e. not mounting like so |
This comment has been minimized.
This comment has been minimized.
pajtai
commented
Nov 11, 2017
•
|
If anyone else runs into this with 2.0.0. The config flag is now, Edit: When I tried to use the config flag in my |
This comment has been minimized.
This comment has been minimized.
mperezco
commented
Feb 2, 2018
|
I have a running RPM deployment that works for Prometheus 2.1.0 ... in case it helps: |
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. |
hryamzik commentedApr 9, 2016
After updating to the latest version consoles stopped working. I do have them on the file system, like
/opt/prometheus/consoles/node.html. There's nothing in logs about this. Do I miss some configuration option at this point?