-
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
runtime error: slice bounds out of range #2150
Comments
Could you share some pcap files of when this happens? Can you also share your config file? Did this happen only once or does this happen more often? |
I saw this while trying to gather information for a different error.
I have a 90GB pcap file that I will try to narrow down to the correct window of time. |
Thank you @codekoala for your help. |
I used editcap to get 5 seconds before and after the timestamp of the error. I'll hold onto the 90GB pcap file for a while just in case the snippet is insufficient. |
@codekoala What kind of traffic are you trying to monitor with Packetbeat? In the attached pcap, I see some REDIS traffic, but no HTTP. It might be that the HTTP parsing error appears when Packetbeat is trying to decode some traffic that is not HTTP. Can you please also share the configuration file with us? |
I've long since obliterated the environment where this was running (including the 90GB pcap dump). I was using a default configuration, only changing the output to go to logstash. Every supported input protocol was enabled, iirc. Packetbeat was simply running on my dev box while working on a different project that used redis. Nothing particularly fancy. I wasn't looking to capture anything specifically, just to see what kind of fun packetbeat brought to my life. I was dumping the .pcap file because I stumbled upon a different error (which I brought up at https://discuss.elastic.co/t/parsememcache-udp-exception-invalid-memory-address-or-nil-pointer-dereference/57956/7) while just letting packetbeat run for a while. |
Aug 2 12:23:28 kvm15 /usr/bin/packetbeat[3973]: log.go:113: ParseHttp exception. Recovering, but please report this: runtime error: slice bounds out of range.
Aug 2 12:23:28 kvm15 /usr/bin/packetbeat[3973]: log.go:114: Stacktrace: /go/src/github.com/elastic/beats/libbeat/logp/log.go:114 (0x4c5a96)#12/usr/local/go/src/runtime/asm_amd64.s:437 (0x47c88e)#12/usr/local/go/src/runtime/panic.go:423 (0x44b119)#12/usr/local/go/src/runtime/panic.go:18 (0x449659)#12/go/src/github.com/elastic/beats/packetbeat/protos/http/http_parser.go:165 (0x4e618c)#12/go/src/github.com/elastic/beats/packetbeat/protos/http/http_parser.go:96 (0x4e4d97)#12/go/src/github.com/elastic/beats/packetbeat/protos/http/http.go:296 (0x4df8d2)#12/go/src/github.com/elastic/beats/packetbeat/protos/http/http.go:229 (0x4df326)#12/go/src/github.com/elastic/beats/packetbeat/protos/tcp/tcp.go:101 (0x52ca31)#12/go/src/github.com/elastic/beats/packetbeat/protos/tcp/tcp.go:164 (0x52d573)#12/go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:183 (0x7137b7)#12/go/src/github.com/elastic/beats/packetbeat/decoder/decoder.go:101 (0x712cf1)#12/go/src/github.com/elastic/beats/packetbeat/sniffer/sniffer.go:356 (0x5417f9)#12/go/src/github.com/elastic/beats/packetbeat/beat/packetbeat.go:232 (0x481d4b)#12/usr/local/go/src/runtime/asm_amd64.s:1696 (0x47ebd1)
The text was updated successfully, but these errors were encountered: