-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
could not get net class info: error obtaining net class info: open /host/sys/class/net/calixxx #1840
Comments
It's probably some sort of permission / dev namespace issue, not an issue in node-exporter itself. I was about to suggest to just ignore them via --collector.netclass.ignored-devices but that would do the filtering only after the error here: https://github.com/prometheus/procfs/blob/master/sysfs/net_class.go#L120 @SuperQ @pgier We could just ignore field not found errors there as well, wdyt? |
SuperQ
added a commit
that referenced
this issue
Mar 3, 2021
* Handle no such file and permission denied errors. * Reduce excessive error wrapping. Fixes: #1840 Signed-off-by: Ben Kochie <superq@gmail.com>
SuperQ
added a commit
that referenced
this issue
Mar 3, 2021
* Handle no such file and permission denied errors. * Reduce excessive error wrapping. Fixes: #1840 Signed-off-by: Ben Kochie <superq@gmail.com>
SuperQ
added a commit
that referenced
this issue
Mar 5, 2021
* Handle no such file and permission denied errors. * Reduce excessive error wrapping. Fixes: #1840 Signed-off-by: Ben Kochie <superq@gmail.com>
oblitorum
pushed a commit
to shatteredsilicon/node_exporter
that referenced
this issue
Apr 9, 2024
* Handle no such file and permission denied errors. * Reduce excessive error wrapping. Fixes: prometheus#1840 Signed-off-by: Ben Kochie <superq@gmail.com>
oblitorum
pushed a commit
to shatteredsilicon/node_exporter
that referenced
this issue
Apr 9, 2024
* Handle no such file and permission denied errors. * Reduce excessive error wrapping. Fixes: prometheus#1840 Signed-off-by: Ben Kochie <superq@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Host operating system: output of
uname -a
Linux ip-10-XX-XXX-XXX.eu-central-1.compute.internal 5.3.0-1023-aws #25~18.04.1-Ubuntu SMP Fri Jun 5 15:18:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
node_exporter version: output of
node_exporter --version
quay.io/prometheus/node-exporter:v1.0.1
(daemonset in k8s)node_exporter command line flags
Are you running node_exporter in Docker?
yes, daemonset in k8s (installed with kube-prometheus)
What did you do that produced an error?
nothing... the error seems to always appear on 1 of the k8s node and only one and seems to cause an alert "NodeDown" to be raised (whereas the node is not down)
What did you expect to see?
no error
What did you see instead?
The text was updated successfully, but these errors were encountered: