Open cmacknz opened 1 day ago
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)
Briefly looking at the logs I can see references such as net.cgoLookupHostIP
, this is the C netdns resolver. We could opt-in to use the netgo resolver.
Edit: The crash seems to be triggered in the call to reflect.implements
https://github.com/elastic/go-ucfg/blob/4fd3937/initializer.go#L39C29-L39C39
Does the issue happen if GODEBUG=netdns=go
set?
Does the issue happen if
GODEBUG=netdns=go
set?
Also wondering about this. The cgo resolver uses threads so in high contention scenarios the netgo resolver might perform better by leveraging goroutines.
Does the issue happen if GODEBUG=netdns=go set?
Confirmed that setting GODEBUG=netdns=go
stops this from happening.
There is a chance that this PR will fix it https://github.com/elastic/beats/pull/41402 The PR updates glibc from 2.28 to 2.31.
We have an internal example of multiple Beats failing shortly after startup with a segmentation fault in CGO code. The exact path leading to this is not clear yet because the problem is in CGO, although we do have the stack trace which is attached.
cgo_segfault.json