Bug #75142 "MySQL 5.6"+"MySQL Proxy"+"MySQL Workbench": Bad handshake
Submitted: 8 Dec 2014 15:45 Modified: 8 Mar 2018 23:38
Reporter: M Heins Email Updates:
Status: Closed Impact on me:
Category:MySQL Proxy Severity:S1 (Critical)
Version:0.8.1 OS:Linux (Ubuntu 12.04 / Ubuntu 14.04)
Assigned to: CPU Architecture:Any
Tags: bad handshake, mysql 5.6, mysql proxy, MySQL Workbench

[8 Dec 2014 15:45] M Heins

if you install a mysql-server-5.6 (Ubuntu 14.04 LTS) and of another system mysql-proxy (Ubuntu 12.04 LTS) then try to have DB-access through the mysql-proxy with MySQL Workbench 6.2.4 (latest) then you get the error:  "Bad handshake"

If you use an MySQL up to 5.5 all is perfect and per command line it works too.

How to repeat:

mysql-proxy --admin-username=dbuser --admin-password=xxxxxxxx --admin-lua-script /usr/lib/mysql-proxy/lua/admin.lua --proxy-backend-addresses=db.domain.de:3306 --daemon --proxy-address=:10060 --admin-address=10061
[9 Dec 2014 18:16] Sveta Smirnova
Thank you for the report.

Which exact version of MySQL Proxy do you use?
[10 Dec 2014 9:04] M Heins

we have al versions from 0.7 (Ubuntu 10.04 LTS) until the neuest one from "Ubuntu 12.04 LTS":

Paket: mysql-proxy                              
Zustand: Installiert
Automatisch installiert: nein
Version: 0.8.1-1.1build1
Priorität: extra
Bereich: universe/misc
Verwalter: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architektur: amd64
Unkomprimierte Größe: 852 k
Hängt ab von: libc6 (>= 2.7), libevent-2.0-5 (>= 2.0.10-stable), libglib2.0-0 (>= 2.24.0), liblua5.1-0
Kollidiert mit: mysql-proxy
Beschreibung: Hochverfügbare Lastverteilung und Abfragenveränderung für MySQL
 MySQL Proxy ist zwischen Datenbankserver und -clients geschaltet und stellt eine Lastverteilung und Ausfallsicherung bereit.
 Eingehende Abfragen können mit Lua-Skripten gefiltert und modifiziert werden.
Homepage: http://forge.mysql.com/wiki/MySQL_Proxy
[10 Dec 2014 9:07] M Heins
> ... until the neuest one from ...

I mean:

... until the newest one from ...
[16 Dec 2014 18:24] Sveta Smirnova
Thank you for the feedback.

Please try with current version 0.8.5 from dev.mysql.com/downloads and inform us if the problem still exists.
[8 Jan 2015 11:31] M Heins
it is not so easy to test the newest (tgz) one in are productive environment...
But I am sure that bug is in 0.8.5 too.

Are work-around is to leave "MySQL Workbenche" and go to "SQLyog" (https://code.google.com/p/sqlyog/wiki/Downloads).
[15 Jan 2015 20:35] Sveta Smirnova
Thank you for the feedback.

I still cannot repeat described behavior. Please try version 0.8.5 and, if problem still exists, provide version of WB you use.
[16 Feb 2015 1: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".
[24 Jun 2015 8:56] Rudolf Cardinal
Bug replicated (using MySQL 5.6.19 under Ubuntu 14.04) with mysql-proxy 0.8.1 (as distributed with that version of Ubuntu). Bug goes away when using mysql-proxy 0.8.5.
[8 Mar 2018 23:38] MySQL Verification Team
Closing according last comment? Bug goes away when using mysql-proxy 0.8.5.