-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Closed
Description
Host operating system: output of uname -a
Linux srv 4.14.78-8.el7.x86_64 #1 SMP Tue Oct 23 15:00:24 IST 2018 x86_64 x86_64 x86_64 GNU/Linux
node_exporter version: output of node_exporter --version
node_exporter, version 0.17.0-rc.0 (branch: HEAD, revision: 751996761903af4cffe18cf2d980b8ae9a202204)
build user: root@c0c3850b6d2b
build date: 20181020-06:27:39
go version: go1.11.1
node_exporter command line flags
without flags
Are you running node_exporter in Docker?
no
What did you do that produced an error?
Just start node exporter with enabled filesystem collector from non-root user
What did you expect to see?
everything is working :)
What did you see instead?
Filesystem collector doesn't working with the following error:
Nov 26 12:32:15 srv node_exporter[2034]: time="2018-11-26T12:32:15+03:00" level=error msg="ERROR: filesystem collector failed after 0.000061s: open /proc/1/mounts: no such file or directory" source="collector.go:132"
File exists and readable only for root.
~ $ ls -l /proc/1/mounts
-r--r--r-- 1 root root 0 Nov 26 12:57 /proc/1/mounts
But in our case node-exporter was executed from a non-root user.
In 0.14.0 the collector worked fine. Would be fine to try another method for retrieving FS metrics as a fallback.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels