Skip to content
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

nfsd collector is default, while documentation states that it isn't a default collector. #820

Closed
corymacd opened this issue Feb 13, 2018 · 2 comments

Comments

@corymacd
Copy link

corymacd commented Feb 13, 2018

Host operating system: output of uname -a

Linux 4.13.0-1007-azure #9-Ubuntu SMP Thu Jan 25 10:47:32 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

node_exporter version: output of node_exporter --version

node_exporter, version 0.15.0 (branch: master, revision: 544488d)
build user: [redacted]
build date: 20180213-15:26:40
go version: go1.6.2

node_exporter command line flags

Are you running node_exporter in Docker?

No.

What did you do that produced an error?

After compiling per documentation, getting regular console errors for nfsd collector

What did you expect to see?

No issues, as I am not using nfs nor expected the collector to be enabled by default

What did you see instead?

ERRO[0233] ERROR: nfsd collector failed after 0.000149s: failed to retrieve nfsd stats: open /proc/net/rpc/nfsd: no such file or directory source="collector.go:136"

@SuperQ
Copy link
Member

SuperQ commented Feb 15, 2018

This was a bug, it's now fixed in the latest master. I will update the README to point out that this is a default collector now.

I recommend building from a release tag to avoid getting random bugs from master. 😄

@corymacd
Copy link
Author

Thanks -- that's what I did once I realized I forgot that step, after submitting the report, but then again, Documentation is generally hard. As a consumer of a given product, I appreciate the quick update! I would have contributed the update, had I known if this was the behavior intended or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants