Skip to content
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.

Sign up for GitHub

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

Jump to bottom

GapInStream(mysql) exception. ... runtime error: index out of range. #180

Closed
NITEMAN opened this issue Jul 15, 2015 · 0 comments
Closed

GapInStream(mysql) exception. ... runtime error: index out of range. #180

NITEMAN opened this issue Jul 15, 2015 · 0 comments
Assignees
@tsg
Labels
bug

Comments

@NITEMAN
Copy link

NITEMAN commented Jul 15, 2015

Yesterday I've switched to beta2 and we're seen on syslog this error quite often (about 3-4 times per hour):

Jul 15 08:06:51 machine /usr/bin/packetbeat[39908]: log_unix.go:123: GapInStream(mysql) exception. Recovering, but please report this: runtime error: index out of range.
Jul 15 08:06:51 machine /usr/bin/packetbeat[39908]: log_unix.go:124: Stacktrace: /home/vagrant/src/github.com/elastic/packetbeat/Godeps/_workspace/src/github.com/elastic/libbeat/logp/log_unix.go:124 (0x466b62)#012/usr/local/go/src/runtime/asm_amd64.s:401 (0x430215)#012/usr/local/go/src/runtime/panic.go:387 (0x41cf88)#012/usr/local/go/src/runtime/panic.go:12 (0x41c11e)#012/home/vagrant/src/github.com/elastic/packetbeat/protos/mysql/mysql.go:713 (0x4f0ecc)#012/home/vagrant/src/github.com/elastic/packetbeat/protos/mysql/mysql.go:664 (0x4ef679)#012/home/vagrant/src/github.com/elastic/packetbeat/protos/mysql/mysql.go:570 (0x4ee2a5)#012/home/vagrant/src/github.com/elastic/packetbeat/protos/mysql/mysql.go:459 (0x4ed5d9)#012/home/vagrant/src/github.com/elastic/packetbeat/protos/mysql/mysql.go:542 (0x4ee0b3)#012/home/vagrant/src/github.com/elastic/packetbeat/protos/tcp/tcp.go:90 (0x50382b)#012/home/vagrant/src/github.com/elastic/packetbeat/protos/tcp/tcp.go:161 (0x504540)#012/home/vagrant/src/github.com/elastic/packetbeat/protos/tcp/tcp.go:331 (0x5066dd)#012/home/vagrant/src/github.com/elastic/packetbeat/sniffer/sniffer.go:314 (0x51568a)#012/home/vagrant/src/github.com/elastic/packetbeat/main.go:237 (0x408d86)#012/usr/local/go/src/runtime/asm_amd64.s:2232 (0x432351)

It seems, for me, a new variant of #140

Please let me know if you need more info or a trace
@tsg tsg mentioned this issue Jul 28, 2015
Merged
@tsg tsg closed this as completed in #188 Jul 28, 2015
ruflin added a commit that referenced this issue Dec 2, 2015
@ruflin
Merge pull request #180 from monicasarbu/fix_title_sections
6d1a23b 
Couple of small fixes to the configuration
tsg pushed a commit to tsg/beats that referenced this issue Jan 20, 2016
Proper error handling code in the mysqlParseResponse function
7e2fdb4 
The problem was that the initial version of this function assumed
that the message is already a valid MySQL message. While indeed
some basic checks on it were made at the layer below (separating
the message out of the TCP stream), there are still plenty of things
that can go wrong.

This adds error handling in (hopefully) all possible branches and
a set of unit tests that exploit most of those.

Closes elastic#180.
tsg pushed a commit to tsg/beats that referenced this issue Jan 20, 2016
@ruflin
Merge pull request elastic#180 from monicasarbu/fix_title_sections
acf53d9 
Couple of small fixes to the configuration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tsg tsg

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tsg @NITEMAN @monicasarbu