-
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
panic: runtime error: slice bounds out of range #4
Comments
Unfortunately the stack trace is not very useful, because all goroutines seem to be waiting for IO or in a system call. Based on the logs it looks like there might be an issue parsing the MySQL messages. Which version of MySQL do you have? Also, if this happens quickly enough, can you please run packetbeat like this? It will add more debugging info: packetbeat -e -c /etc/packetbeat/packetbeat.conf -d mysql,mysqldetailed Thanks. |
It happens quickly enough, hope this helps gaining insights:
MySQL in this case means Percona 5.5. |
Hello, I'm seeing this error as well, it randomly crashes, with mysql 5.0 on Centos 5.9 using the binary package. Also I'm trying it in FreeBSD 9 and one time it crashed with the same error but parsing http (nginx proxy), although only happened once for now (in a server with 3000 reqs/minute):
|
We have just released v0.1.1 which should not crash anymore in these cases. Instead it will print a stacktrace to the logs and continue. Please continue to post us the stacktraces if you see them in the logs. Btw, I'm glad to hear that it works in FreeBSD, apart of the above issues :). |
There was a bug in the chunked encoding handling when the segment boundary is between \r and \n. This adds a test to show the issue and the code to fix it.
Remove all links until project is mature.
Makefile, template and Godeps
Renamed -config param to -configDir and make it optional. Everything …
adding ability to pass in IP of elasticsearch host as an input
Add a new dashboard for topbeat
Use Travis to build packages and upload them to S3
There was a bug in the chunked encoding handling when the segment boundary is between \r and \n. This adds a test to show the issue and the code to fix it.
bool -> boolean for field declaration
…libs-main_2022_01_19-14_07_47 [jjbb][beats-ci] elastic-agent-libs
* handle EOF on single line content (#33568) * handle EOF on single line content * changelog * fallback to encode_eof if no events in aws-s3 input * lint * lint * collect on EOF in line reader * remove encode eof * remove iterN * fix test * increase test coverage * linting * more linting * increase coverage (cherry picked from commit 7b45320) # Conflicts: # libbeat/reader/readfile/line.go # libbeat/reader/readfile/line_test.go # x-pack/filebeat/input/awss3/s3_objects.go * Fix conflicts * Fix failing test - TestMaxBytesLimit * Fix #2 failing test - TestMaxBytesLimit * Fix failing test checks * Fix linter errors * Fix typo * Fix linter errors #2 * Fix linter errors #3 * Fix linter errors #4 * Fix linter errors #5 * Changelog clean up * Change order of publish event --------- Co-authored-by: Andrea Spacca <[email protected]> Co-authored-by: Tamara Dancheva <[email protected]>
I haven't captured the packets that created this (as I have no clue what exactly caused this), but maybe the traceback already helps...?
Cheers
Stephan
The text was updated successfully, but these errors were encountered: