node_exporter
                                
                                 node_exporter copied to clipboard
                                
                                    node_exporter copied to clipboard
                            
                            
                            
                        Node exporter crash with textfile collector turned on in 1.0.1 and 1.1.1 on OS X 10.9.5
Host operating system: output of uname -a
Darwin 
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
Current workaround is to run node exporter without the textfile collector
@appleciderjack Can you try the workaround linked to in the issue you linked? https://github.com/evanw/esbuild/issues/81#issuecomment-680147925 But there isn't much we can do on our side. Maybe we could document this if you can confirm it to be working.