MySQL Bugs: #30307: mysql-proxy crashes with: file network-mysqld-proto.c: line 94 (network_mysqld

Bug #30307	mysql-proxy crashes with: file network-mysqld-proto.c: line 94 (network_mysqld_p
Submitted:	8 Aug 2007 13:58	Modified:	7 Oct 2007 7:38
Reporter:	Jeremy Kusnetz	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Proxy	Severity:	S1 (Critical)
Version:	6.0	OS:	Linux (Slackware 10.0)
Assigned to:		CPU Architecture:	Any

Description:
We have a mysql application that connects to a mysql server through stunnel. The application can be called hundreds of times each time opening up a new connection and thus a new stunnel. mysql-proxy seems to be a great solution for this problem.

I'm running the latest SVN as of 8/7/2007. when testing a proxy-port that the application doesn't connect to everything seems fine, but as soon as I start mysql-proxy on the mysql port the application uses, mysql-proxy dies:

file network-mysqld-proto.c: line 94 (network_mysqld_proto_skip): assertion failed: (*_off + size <= packet->len)
Aborted

Should I open a bug, or is something I'm doing wrong?

mysql-proxy --proxy-backend-addresses=sql:3311 --proxy-address=:3310

3310 is what's normally stunneled, so I changed stunnel to listen to 3310 and set mysql proxy to listen to 3310.

How to repeat:
run the proxy with our setup?

strace of crash

Attachment: mysql-proxy-bug30307-strace.txt (text/plain), 23.08 KiB.

Thank you for the report.

I can not repeat described behaviour with revision 153 and other Tunnel tool (SSHKeychain). Please indicate revision number you get error with and provide command you use to run stunnel.

Sorry for the delay on this, the last one I tried was 200.

This proxy was compiled with 5.0 libraries, but it's a 4.1 client talking to it.  I saw a message on the forums that this could happen with a 4.1 client?

There isn't much in the stunnel command line, it's using a conf file.  There isn't anything special in the config, just listens on one port, stunnels to another server on another port.

Thank you for the feedback.

I still can not repeat described behaviour with revision 225.

Please try with this revision and if you can repeat provide step-by-step instruction how you set up the environment.

I have the same problem with the latest release mysql-proxy-0.6.0-linux-rhas4-x86 when put PowerDNS to use mysql-proxy as a backend. There are about 6000 records in PowerDNS database.

I have the same problem with the latest release mysql-proxy-0.6.0-linux-rhas4-x86 when put PowerDNS to use mysql-proxy as a backend. There are about 6000 records in PowerDNS database.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".