MySQL Bugs: #74960: SSH fails to connect

Bug #74960	SSH fails to connect
Submitted:	21 Nov 2014 12:22	Modified:	27 Sep 2015 0:01
Reporter:	Steven Azari	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	6.2.4	OS:	Linux (Ubuntu 14.04.1 LTS)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
----[For better reports, please attach the log file after submitting. You can find it in /home/sazari/.mysql/workbench/log/wb.log]

11:36:07 [ERR][sshtunnel.py:notify_exception_error:233]: Traceback (most recent call last):
  File "/usr/share/mysql-workbench/sshtunnel.py", line 315, in accept_client
    sshchan = transport.open_channel('direct-tcpip', self._target, local_sock.getpeername())
  File "/usr/lib/mysql-workbench/modules/wb_admin_ssh.py", line 116, in wba_open_channel
    raise e
EOFError

How to repeat:
Try connecting via SSH and it gives the above error in logs.

Setting SSH on Ubuntu

Attachment: ssh_centos_from_ubuntu.png (image/png, text), 442.27 KiB.

Thank you for the bug report. I couldn't repeat connecting with a CentOS 6.5 (see attached picture with SSH setup connection) below my log:

11:29:05 [WRN][sshtunnel.py:wait_connection:424]: Host_keys directory is missing, recreating it
11:29:05 [WRN][sshtunnel.py:wait_connection:427]: Host_keys file is missing, recreating it
11:29:05 [WRN][sshtunnel.py:wait_connection:430]: Successfully saved host_keys file.
11:29:05 [INF][     SSH tunnel]: TunnelManager.wait_connection server key stored, retrying: Server key has been stored
11:29:05 [WRN][     SSH tunnel]: Opening SSH tunnel: Retry due to fingerprint missing, user accept new fingerprint
11:29:05 [INF][     SSH tunnel]: Existing SSH tunnel not found, opening new one
11:29:05 [INF][     SSH tunnel]: Opening SSH tunnel to 192.168.2.104:22
11:29:05 [INF][     SSH tunnel]: TunnelManager.wait_connection returned OK
11:29:05 [INF][sshtunnel.py:set_keepalive:471]: SSH KeepAlive setting skipped.
11:29:05 [INF][     SSH tunnel]: SSH tunnel connect executed OK

Hi,

I have the same problem with:

(K)ubuntu 14.10 x64 - kde4
Mysql Workbench 6.2.4 installed from MySQL APT Repository (mysql-apt-config_0.3.2-1ubuntu14.04_all.deb)

Had exactly the same issue on MySQL-WB 6.2.4/Ubuntu 14.04/Python 2.7.6 after upgrading Paramiko to 1.15.1, downgrading back to 1.14.1 with pip fixed the issue for me.

Also there is this in the changelog of 6.2.4:
https://dev.mysql.com/doc/relnotes/workbench/en/wb-news-6-2-4.html

Bugs Fixed
...

Connections to remote hosts using the connection method "Standard TCP/IP over SSH" would fail with new versions (1.15+) of the paramiko library.

A workaround was to downgrade the system's paramiko library. (Bug #19768621, Bug #74223)

Maybe we have an early 6.2.4 build or the fix doesn't work.

sounds about right. I don't fancy rolling back parmaiko, so in the mean time, I'm just creating a background ssh to my local and using normal tcp to my local address.

Patched in Debian

This Launchpad ticket has a patch :

https://bugs.launchpad.net/ubuntu/+source/mysql-workbench/+bug/1385147

Patch here : 

https://launchpadlibrarian.net/189450207/paramiko.patch

Owing to other API problems on 14.10 have build from source. Source seems to contain a partial patch - it tests for the Paramiko version numbers, but doesn't set the default window and packet sizes in the event the version is higher than 14, 99 

Applied the patch by hand (patch as presented won't work on 6.2.4 source archive) and it works (happily it's Python script so no rebuilds).

Is it possible that this bug is a duplicate of https://bugs.mysql.com/74658 ?

Please check for duplicate with https://bugs.mysql.com/bug.php?id=74658. Thanks.

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".