Bug #30856 When MySQL TOAD tries to connect MySQL Proxy crashes
Submitted: 6 Sep 2007 11:24 Modified: 1 Mar 2008 9:18
Reporter: Prashant Varshney Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Proxy: Core Severity:S1 (Critical)
Version:0.5.1 OS:Linux
Assigned to: CPU Architecture:Any

[6 Sep 2007 11:24] Prashant Varshney
Description:
Whenever I try to connect MySQL TOAD to the server through MySQL Proxy, it crashes by giving this error.

file network-mysqld-proto.c: line 144 (network_mysqld_proto_get_string): assertion failed: (*(packet->str + *_off + len) == '\0')

Please provide help.

How to repeat:
Try to connect MySQL TOAD. It is repeatable.
[6 Sep 2007 11:33] Jan Kneschke
Are you using a pre-4.1 password or a empty password ?

(pre-4.1 means that the password-hash starts NOT with * in the mysql.user table)
[6 Sep 2007 12:03] Prashant Varshney
A little more detail related to the problem.

My password is 'monty'.

MySQL version = Server version: 5.0.41-log MySQL Community Server (GPL)
[6 Sep 2007 12:31] Jan Kneschke
Please never paste any passwords, the bug-system is world-readable.

I only wanted to know if you are using the old or the new password style for this account:

> select user, host, length(password) from mysql.user;
+------------------+
| length(password) |
+------------------+
|               41 |  <- a new style password
|               16 |  <- a old style password
|                0 |  <- a empty password
+------------------+

Can you check what kind of password-hash you have ? (don't paste it here, just check)
[6 Sep 2007 13:04] Prashant Varshney
Thanks for the advice. The system is still on test-bed so it is not a problem.

However, the output of the query in my case says 41.

Is there any clue as to why the problem may be occurring.
[1 Feb 2008 9:18] Valeriy Kravchuk
Please, try to repeat with a newer version of Proxy, 0.6.0, and inform about the results.
[2 Mar 2008 0:00] Bugs System
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".