Document PuTTY based tunneling workaround for accessing labsdb via older MySQLBench versions
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	yuvipanda
	May 21 2015, 7:13 PM

Description

Older versions of MySQL Bench are broken due to https://gerrit.wikimedia.org/r/#/c/185329 and https://gerrit.wikimedia.org/r/#/c/185321/. Workaround for this is to:

Upgrade to a newer version (and someone should test to see if these work fine)
Use putty to establish the ssh tunnel, and then point mysql workbench at the ssh tunnel (http://realprogrammers.com/how_to/set_up_an_ssh_tunnel_with_putty.html and similar have generic instructions)
Use quarry.wmflabs.org (this only for readonly labsdb queries)

Event Timeline

yuvipanda created this task.May 21 2015, 7:13 PM

yuvipanda raised the priority of this task from to Needs Triage.

yuvipanda updated the task description. (Show Details)

yuvipanda added a project: Cloud-Services.

yuvipanda subscribed.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMay 21 2015, 7:13 PM

yuvipanda renamed this task from Document PuTTY based tunneling workaround for accessing labsdb via ancient MySQLBench versions to Document PuTTY based tunneling workaround for accessing labsdb via older MySQLBench versions.May 21 2015, 7:16 PM

yuvipanda set Security to None.

Apparently an issue with older Paramiko versions. Possible workaround:

download a more recent paramiko, e.g. https://github.com/paramiko/paramiko/archive/1.15.zip
copy the paramiko directory to c:\program files (x86)\MySQL Workbench 6.3.3 CE (win32)\python\site-packages, overwriting the existing directory.

Betacommand subscribed.May 21 2015, 8:12 PM

valhallasw: That does not work. Are there any dependencies that need to be installed?

14:01 < mutante> well the error message you had before the update was related to the ciphers
14:01 < mutante> and after the update it's just in general about opening a tunnel
14:01 < mutante> so that would mean the paramiko update fixed the cipher issue
14:03 < mutante> can you paste both error messages for me once?

14:04 < Superyetkin> first error: no kex algorithm, etc.
14:04 < Superyetkin> seconf: cannot open SSH tunnel ....

So i would say we have found out what fixes the issue with us now using different key exchange protocols: upgrading paramiko as described by valhallasw. (thanks!)

Unfortunately there is now a remaining issue with setting up the SSH tunnel. This should not be related to our recent changes but remains to be solved. We'll need some more troubleshooting on a Windows machine.

http://homer.netsal.selu.edu/mediawiki/index.php/Creating_a_SSH_tunnel_to_MySql_using_PuTTY_-_Tyler_Hunt worked for me by having putty open 127.0.0.1:3306 as a tunnel to a *.labsdb:3306 host.

I have got the MySQL Wokbench 5.2.24 CE to work by discarding its SSH tunneling features. One needs to establish the PuTTY-generated tunnel and select "TCP/IP" as connection method in MW. Thanks to all who helped out with this.

• Phabricator_maintenance removed a subscriber: yuvipanda.Jun 7 2017, 6:51 PM

Document PuTTY based tunneling workaround for accessing labsdb via older MySQLBench versionsClosed, ResolvedPublicActions

Description

Event Timeline

Document PuTTY based tunneling workaround for accessing labsdb via older MySQLBench versions
Closed, ResolvedPublic
Actions