Bug #62119 workbench assumes a windows mysql server if ip is 127.0.0.1 -> breaks portfw

• Submitted: 9 Aug 2011 0:35
• Modified: 23 Jul 2012 23:07
• Reporter: hans mueller
• Status: Closed
• Category: MySQL Workbench
• Severity: S3 (Non-critical)
• Version: 5.2.34
• OS: Windows (7x64)
• CPU Architecture: Any
• Tags: linux, localhost, portforward, remote, windows

[9 Aug 2011 0:35] hans mueller

Description:
on a windows host workbench assumes that the mysql server is a windows server if the localhost ip is used (127.0.0.1) also if "remote host" is defined at "new server instance". 

this breaks local portforwarding to a linux machine. 

in "test db connection" the server type is correctly detected (version: 5.1.49-3, server os: linux)

the new instance wizard stucks at "windows management", where it looks for a local windows service which simply not exists.

(it only works if i connect to the lan ip of the host)

How to repeat:
on windows c

workbench
server administration
new server instance

specify host machine
- remote host -> 127.0.0.1

database connection
- 127.0.0.1
- standard tcp/ip
- hostname: 127.0.0.1
- port: 3306
- root

test db connection
-> open databse connection
-> get server version: 5.1.49-3
-> get server os: linux

next jumps to 
"windows management" without the option to force a remote connection

Suggested fix:
user should be able to specify if 127.0.0.1 is local or not. also an option to skip the windows management would be good. 
manually defining the instance type would also be fine.

[19 Aug 2011 1:37] Alfredo Kojima

The detection is doing what it is expected to do, but it should not freeze in any case. If no server is found running, it should just offer DB only management.

As a workaround, create the instance from the editor in the Manage Server Instances link.

[19 Aug 2011 19:53] Joel Kershner

Same problem however it assumes that I am on a windows platform and gives an error :

Error starting workbench adminsitrator
Exception Unsupported administration target type: ('windows','linux','wmi')

When I edit the object it auto selects back to windows as the platform and will not allow me to change that.

[23 Jul 2012 23:08] Philip Olson

This has been fixed as of the soon-to-be-released Workbench 5.2.41, and 
here's the changelog entry:

Detection of a connection to the local machine based on the IP
address has been removed. There is now a selection between
localhost, remote host, and db host on the initial "New
Server Instance" page. Selecting localhost will let
the wizard know that it is local, as otherwise the full path is
now required, which for example allows 127.0.0.1 to be used as a
remote host to support port forwarding.