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
Not collect external hdd #2680
Comments
I assume that you've noticed this in the node_exporter README:
Having said that, you can get more info about why node_exporter reports an error for that filesystem / mountpoint by setting your log level to debug. I expect that you will see an error message of "Error on statfs() system call", and that this is most likely due to the fact that you are not binding the |
We should really remove that Docker warning now that Docker support is better handled. We officially support Docker, but "careful use" so that the host system is taken into consideration is done. |
That appears to be a Docker Compose configuration. Please see the Docker Compose example in the README for correct usage. For questions/help/support please use our community channels. There are more people available to potentially respond to your request and the whole community can benefit from the answers provided. |
My solution was: @dswarbrick was right, in debug logs I saw monitoring-node-exporter | ts=2023-05-08T08:44:53.860Z caller=filesystem_linux.go:96 level=debug collector=filesystem msg="Error on statfs() system call" rootfs=/host/media/nvidov/external_hdd err="permission denied" because of $USER was nobody Thanks all for help |
Host operating system: output of
uname -a
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
node_exporter version: output of
node_exporter --version
node_exporter, version 1.5.0 (branch: HEAD, revision: 1b48970)
build user: root@6e7732a7b81b
build date: 20221129-18:59:41
go version: go1.19.3
platform: linux/arm64
node_exporter command line flags
node_exporter log output
Are you running node_exporter in Docker?
yes
What did you do that produced an error?
$ curl localhost:9100/metrics | grep filesystem_device_error | grep fuse
node_filesystem_device_error{device="/dev/sdb2",fstype="fuseblk",mountpoint="/media/nvidov/external_hdd"} 1
node_filesystem_device_error{device="gvfsd-fuse",fstype="fuse.gvfsd-fuse",mountpoint="/run/user/1000/gvfs"} 1
What did you expect to see?
$ curl localhost:9100/metrics | grep filesystem_device_error | grep fuse
node_filesystem_device_error{device="gvfsd-fuse",fstype="fuse.gvfsd-fuse",mountpoint="/run/user/1000/gvfs"} 1
I bought an external hdd drive "WD My Passport", connected via usb3.0 port to my raspberry pi 4. It automatically mounts in /media/nvidov with the type fuseblk (on macos it is defined as Macos Extended, like in the picture below). When you reformat it to another fstype, rpi starts to work very slowly and the disk speed drops significantly. The logs are empty. I don't know where to look.
Thanks for help
The text was updated successfully, but these errors were encountered: