-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
packetbeat SIGSEV segmentation violation #26014
Comments
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
I'd have to delve into the protocol a bit more to see what we should be doing here, but it looks like we're failing to beats/packetbeat/protos/memcache/memcache.go Lines 344 to 347 in a300f1b
Here's the code from the included stacktrace. First, the call to beats/packetbeat/protos/memcache/plugin_udp.go Lines 210 to 214 in a300f1b
Next, passing that on to beats/packetbeat/protos/memcache/memcache.go Lines 198 to 201 in a300f1b
Passing it on and invoking a method on it: beats/packetbeat/protos/memcache/memcache.go Lines 203 to 207 in a300f1b
Dereferencing it as a part of a debug statement -- beats/packetbeat/protos/memcache/memcache.go Lines 386 to 387 in a300f1b
I'm going to assume we probably just want to no-op the transaction if for some reason it's |
Hi! We're labeling this issue as |
:+1 |
Hi! We're labeling this issue as |
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
Hi! We're labeling this issue as |
Fixed by #33853 |
OS: UnRaid 6.9.3 running Docker Version 20.10.5
Packetbeat version: 7.13.0
I am running packetbeat 7.13.0 on unraid 6.9.3 with a Docker container. I've attached the packetbeat.yml, the log details that show up.
From the monitoring tab I cannot see anything wrong. I debugged packetbeat with the
--httpproof
option here you go:packetbeatdebug.zip I collected the following each minute:
http://192.168.0.252:8888/debug/pprof/heap?gc=1
The issue is that it happens at random.
Packetbeat.yml
Docker details
Detailed error log
process information log event
The text was updated successfully, but these errors were encountered: