| Bug #60383 | Unable to use SSH tunnel to manage server instance | ||
|---|---|---|---|
| Submitted: | 8 Mar 2011 7:15 | Modified: | 18 Aug 2011 10:13 |
| Reporter: | Lee Clemens | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench: Administration | Severity: | S1 (Critical) |
| Version: | 5.2.33 CE Rev 7508 | OS: | Windows (XP SP3) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | foward, localhost, port, ssh, tunnel | ||
[8 Mar 2011 12:18]
Valeriy Kravchuk
Please, check if the same problem still happens with a newer version, 5.2.32.
[8 Mar 2011 15:42]
Lee Clemens
After installing .Net 4, as required by the new minor version - query connection is successful (it was previously as well), but Workbench crashes when I try to connect for Server Administration
[9 Mar 2011 0:37]
MySQL Verification Team
Thank you for the feedback. So the original bug report don't exists anymore instead it is a crash?. Thanks in advance.
[9 Mar 2011 21:03]
Lee Clemens
Is the original bug report description by design? If so, simply fixing the crash will not resolve the original issue. But then, it probably shouldn't crash either. The original issue may still exist, but it crashes before it would occur in the latest version.
[5 Apr 2011 15:34]
MySQL Verification Team
Please try version 5.2.33. Thanks.
[5 May 2011 23: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".
[6 May 2011 1:34]
Lee Clemens
Does not work, now MySQL Workbench crashes: MySQL Workbench has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something, the information you were working on might be lost.
[6 May 2011 1:36]
Lee Clemens
Should say, still crashes (started crashing as of 5.2.32)
[24 May 2011 19:19]
Alfredo Kojima
How are you creating the SSH Tunnel? For administration, you should use the tunnelling support from Workbench itself.
[24 Jun 2011 23: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".
[17 Jul 2011 13:03]
Lee Clemens
SSH Tunnel is created with PuTTY. The error does not appear to indicate the issue is with 'how' the SSH tunnel is created, but rather that is is connecting to 'localhost'.
[18 Jul 2011 10:13]
Valeriy Kravchuk
Do you see the same problem with version 5.2.34.2?
[18 Aug 2011 23: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".
Description: I have a remote MySQL server, which listens on 127.0.0.1. To connect to it remotely, I create an SSH tunnel, forwarding a local port to localhost's port where MySQL is listening. I can create a SQL Development connection properly and query the database. However, I cannot create a Manage Server instance, as Native Windows and SSH login base management options are disabled (presumably because the MySQL Connection includes @localhost - which is Windows), and using the only option "Do not use remote management" results in "Exception: Unsupported administration target type: ('windows', 'linux', 'wmi')" How to repeat: Remote server running Linux and MySQL with bind-address of 127.0.0.1 and port 3306 Client running Windows and MySQL Workbench Create SSH Tunnel with port forwarding, local port 3306 forwarded to remote server's MySQL Server port (localhost:3306) Attempt to connect using MySQL Connection using localhost:3306 (Success) Attempt to connect using same MySQL Connection to Manage Server (Failure) Suggested fix: Do not presume localhost should disable SSH (localhost is Windows, but using port forwarding in this case). Still allow the SSH option to enter remote host/port to use for SSH. Or utilize the tunnel which already exists.