prometheus / prometheus/node_exporter
nfs server stop,but nfs client is mountiong,node_export is down
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.8k
- Forks
- 2.7k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 8
Description
Host operating system: output of uname -a
3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
node_exporter version: output of node_exporter --version
node_exporter command line flags
Are you running node_exporter in Docker?
What did you do that produced an error?
time="2018-08-28T15:22:07+08:00" level=error msg="Error on statfs() system call for "/run/user/0": no such file or directory" source="filesystem_linux.go:57"
time="2018-08-28T15:22:07+08:00" level=error msg="Error on statfs() system call for "/run/user/0": no such file or directory" source="filesystem_linux.go:57"
time="2018-08-28T15:22:07+08:00" level=error msg="Error on statfs() system call for "/run/user/0": no such file or directory" source="filesystem_linux.go:57"
when I umount nfs directory, node_export is eroor and not connect!!!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read filesystem_linux.go around line 57 and reproduce the failure by unmounting the NFS directory while node_exporter runs. Verify whether the statfs error for /run/user/0 is related to the exporter becoming unreachable; a complete report should include the version, flags, and a reproducible result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100