Closed Evesy closed 6 months ago
Looks like a go issue.. I found https://github.com/golang/go/issues/40368 but that is suppose to be fixed for a while..
Maybe related to #2705
Please test the latest release: https://github.com/prometheus/node_exporter/releases/tag/v1.6.1
...
goroutine 1 [semacquire, 119 minutes]:
runtime.gopark(0xce8f00?, 0xc000040030?, 0x0?, 0x80?, 0x6?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc00010f950 sp=0xc00010f930 pc=0x43ba76
runtime.goparkunlock(...)
/usr/local/go/src/runtime/proc.go:387
runtime.semacquire1(0xc000145890, 0x40?, 0x1, 0x0, 0xe0?)
/usr/local/go/src/runtime/sema.go:160 +0x20f fp=0xc00010f9b8 sp=0xc00010f950 pc=0x44cdaf
sync.runtime_Semacquire(0xc0000061a0?)
/usr/local/go/src/runtime/sema.go:62 +0x27 fp=0xc00010f9f0 sp=0xc00010f9b8 pc=0x46ac07
sync.(*WaitGroup).Wait(0x7f2bec846501?)
/usr/local/go/src/sync/waitgroup.go:116 +0x4b fp=0xc00010fa18 sp=0xc00010f9f0 pc=0x48a76b
golang.org/x/sync/errgroup.(*Group).Wait(0xc000145880)
/go/pkg/mod/golang.org/x/sync@v0.2.0/errgroup/errgroup.go:53 +0x27 fp=0xc00010fa30 sp=0xc00010fa18 pc=0x92c867
github.com/prometheus/exporter-toolkit/web.ServeMultiple({0xc0001f3a00, 0x1, 0x7ffe4b72d247?}, 0xc0001f1770, 0xc0001ea3c0, {0xce3360?, 0xc000043a00})
/go/pkg/mod/github.com/prometheus/exporter-toolkit@v0.10.0/web/tls_config.go:235 +0x151 fp=0xc00010fa80 sp=0xc00010fa30 pc=0x92f831
github.com/prometheus/exporter-toolkit/web.ListenAndServe(0x11381a0?, 0xc0001ea3c0, {0xce3360, 0xc000043a00})
/go/pkg/mod/github.com/prometheus/exporter-toolkit@v0.10.0/web/tls_config.go:268 +0x488 fp=0xc00010fb58 sp=0xc00010fa80 pc=0x92fd88
main.main()
/app/node_exporter.go:210 +0x164e fp=0xc00010ff80 sp=0xc00010fb58 pc=0xa645ee
runtime.main()
/usr/local/go/src/runtime/proc.go:250 +0x207 fp=0xc00010ffe0 sp=0xc00010ff80 pc=0x43b647
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc00010ffe8 sp=0xc00010ffe0 pc=0x46ec01
...
This seems to stem from https://github.com/prometheus/exporter-toolkit/blob/v0.10.0/web/tls_config.go#L273. I believe this can be closed as its not specific to node_exporter
(but to exporter-toolkit
), given this bug still exists (cc @Evesy).
@rexagod I think you're reading the stacktrace backwards. The error starts within /usr/local/go/src/runtime/proc.go
. The exporter-toolkit is the end of the trace, basically the victim.
Unrelated, I do think this issue can be closed, we've had no more reports since 1.6.1.
Related https://github.com/prometheus/node_exporter/issues/1881
Host operating system: output of
uname -a
Linux gke-delivery-platform-normal-20220831-b14ed261-plov 5.15.89+ #1 SMP Sat Mar 18 09:27:02 UTC 2023 x86_64 Intel(R) Xeon(R) CPU @ 2.60GHz GenuineIntel GNU/Linux
node_exporter version: output of
node_exporter --version
1.6.0
node_exporter command line flags
node_exporter log output
Are you running node_exporter in Docker?
Kubernetes pod
What did you do that produced an error?
Node exporter attempted to startup on a new node
What did you expect to see?
What did you see instead?