prometheus / prometheus/node_exporter
Node exporter crash with textfile collector turned on in 1.0.1 and 1.1.1 on OS X 10.9.5
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
Darwin 13.4.0 Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64
node_exporter version: output of node_exporter --version
node_exporter, version 1.0.1 (branch: HEAD, revision: 3715be6ae899f2a9b9dbfd9c39f3e09a7bd4559f)
build user: root@4c8e5c628328
build date: 20200616-12:52:07
go version: go1.14.4
node_exporter command line flags
/opt/node_exporter_tls/bin/node_exporter_tls --web.config=/etc/node_exporter_tls/ssl/web-config.yml --web.listen-address=:9100 --collector.textfile.directory=/etc/node_exporter_tls/textfile/
Are you running node_exporter in Docker?
Nope
What did you do that produced an error?
Start program with --collector.textfile.directory=/etc/node_exporter_tls/textfile/, then curl the metrics endpoint.
What did you expect to see?
Successful scrape
What did you see instead?
curl: (7) Failed connect to localhost:9100; Connection refused
On the old window:
dyld: lazy symbol binding failed: Symbol not found: _fdopendir$INODE64
Referenced from: /opt/node_exporter_tls/bin/node_exporter_tls
Expected in: /usr/lib/libSystem.B.dylib
dyld: Symbol not found: _fdopendir$INODE64
Referenced from: /opt/node_exporter_tls/bin/node_exporter_tls
Expected in: /usr/lib/libSystem.B.dylib
SIGTRAP: trace trap
PC=0x7fff6757409d m=7 sigcode=1
goroutine 0 [idle]:
syscall.syscallPtr(0x40b1030, 0xa, 0x0, 0x0, 0x0, 0x0, 0x0)
/usr/local/go/src/runtime/sys_darwin.go:96 +0x2e fp=0xc000053888 sp=0xc000053860 pc=0x40553ae
Possibly related to:
https://github.com/golang/go/issues/35269
Since this is a 10.9.5 system
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
Start by reproducing the crash with the node_exporter binary on OS X 10.9.5, using --collector.textfile.directory and then requesting the metrics endpoint. Read the related Go issue about _fdopendir$INODE64 and trace the textfile collector's directory access. Done means the exporter starts and serves a successful scrape without the dyld or SIGTRAP failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- observability-sre, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100