Bug #81459 cannot connect to database server from workbench
Submitted: 17 May 2016 9:57 Modified: 17 May 2016 12:28
Reporter: qian wang Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S5 (Performance)
Version:6.3.6 OS:Windows (Microsoft Windows 7 Enterprise Service Pack 1)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[17 May 2016 9:57] qian wang 
Description:
when open workbench and try to open the base, error message Could not open database
but this is not a because the service is down or the pwd is wrong.I can connect to the base from command line mysql and run all sql(select, delete, insert...) by command line

 
there is the log:

11:20:22 [ERR][      Workbench]: Console redirection failed.
11:20:22 [INF][      WBContext]: Parsing application arguments.
11:20:22 [INF][      WBContext]:     C:\Program Files\MySQL\MySQL Workbench 6.3 CE\MySQLWorkbench.exe
11:20:22 [INF][      Workbench]: Starting up Workbench
11:20:22 [INF][      Workbench]: Current environment:
	Command line: "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\MySQLWorkbench.exe" 
	.....
:\cygwin64\bin;C:\Program Files\nodejs\;C:\Program Files (x86)\MySQL\MySQL Fabric 1.5 & MySQL Utilities 1.5\;C:\Program Files (x86)\MySQL\MySQL Fabric 1.5 & MySQL Utilities 1.5\Doctrine extensions for PHP\;C:\Utilisateurs\A573027\AppData\Roaming\npm;C:\Javatools\java\jdk1.8.0_45\bin
11:20:22 [INF][ mforms managed]: Initializing mforms wrapper
11:20:22 [INF][   WBContext UI]: Initializing workbench context UI with these values:
	base dir: C:\Program Files\MySQL\MySQL Workbench 6.3 CE
	plugin path: C:\Program Files\MySQL\MySQL Workbench 6.3 CE
	struct path: 
	module path: C:\Program Files\MySQL\MySQL Workbench 6.3 CE/modules
	library path: C:\Program Files\MySQL\MySQL Workbench 6.3 CE
	user data dir: C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench
	......
11:20:24 [INF][            WBA]: Looking for extension modules for WBA...
11:20:24 [INF][            WBA]: 0 extension modules found
11:20:24 [WRN][            grt]: C:\Program Files\MySQL\MySQL Workbench 6.3 CE\data/table_templates.xml:21: link 'com.mysql.rdbms.mysql.datatype.timestamp' <object db.SimpleDatatype> key=simpleType could not be resolved
11:20:24 [WRN][            grt]: C:\Program Files\MySQL\MySQL Workbench 6.3 CE\data/table_templates.xml:106: link 'com.mysql.rdbms.mysql.datatype.varchar' <object db.SimpleDatatype> key=simpleType could not be resolved
11:20:24 [WRN][            grt]: C:\Program Files\MySQL\MySQL Workbench 6.3 CE\data/table_templates.xml:229: link 'com.mysql.rdbms.mysql.datatype.int' <object db.SimpleDatatype> key=simpleType could not be resolved
11:20:24 [INF][            grt]: Scanning module directory C:\Program Files\MySQL\MySQL Workbench 6.3 CE.	
11:20:24 [WRN][            grt]: C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench\connections.xml:26: link '{DA9FDD49-FD36-4C7A-AF5B-CC2D0C6FAAC3}' <object GrtObject> key=owner could not be resolved
11:20:24 [INF][      WBContext]: System info:
 	MySQL Workbench Community (GPL) for Windows version 6.3.6 CE build 511 (64 bit)
	Configuration Directory: C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench
	Data Directory: C:\Program Files\MySQL\MySQL Workbench 6.3 CE
	.....

11:20:24 [INF][    WQE backend]: Found auto-save workspace C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench\sql_workspaces\Local_instance_wampmysqld64-1.autosave
11:20:24 [WRN][    WQE backend]: Found incomplete auto-save workspace C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench\sql_workspaces\unconnected-1.autosave
11:20:24 [WRN][    WQE backend]: Found incomplete auto-save workspace C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench\sql_workspaces\unconnected-10.autosave
11:20:24 [WRN][    WQE backend]: Found incomplete auto-save workspace C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench\sql_workspaces\unconnected-11.autosave
11:20:24 [WRN][    WQE backend]: Found incomplete auto-save workspace C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench\sql_workspaces\unconnected-12.autosave
11:20:24 [WRN][    WQE backend]: Found incomplete auto-save workspace C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench\sql_workspaces\unconnected-13.autosave
11:20:24 [WRN][    WQE backend]: Found incomplete auto-save workspace C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench\sql_workspaces\unconnected-14.autosave
11:20:24 [WRN][    WQE backend]: Found incomplete auto-save workspace C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench\sql_workspaces\unconnected-15.autosave
11:20:24 [WRN][    WQE backend]: Found incomplete auto-save workspace C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench\sql_workspaces\unconnected-16.autosave
......

11:20:24 [WRN][    WQE backend]: Found incomplete auto-save workspace C:\Utilisateurs\A573027\AppData\Roaming\MySQL\Workbench\sql_workspaces\unconnected-9.autosave
11:20:24 [INF][      Workbench]: UI is up
11:20:25 [INF][      Workbench]: Running the application
11:20:28 [ERR][      SqlEditor]: SQL editor could not be connected: Could not open database
11:20:28 [ERR][      SqlEditor]: Your connection attempt failed for user 'root' from your host to server at 127.0.0.1:3306:
  Could not open database

Please:
1 Check that mysql is running on server 127.0.0.1
2 Check that mysql is running on port 3306 (note: 3306 is the default, but this can be changed)
3 Check the root has rights to connect to 127.0.0.1 from your address (mysql rights define what clients can connect to the server and from which machines) 
4 Make sure you are both providing a password if needed and using the correct password for 127.0.0.1 connecting from the host address you're connecting from

How to repeat:
when open workbench and try to open the base, error message Could not open database
[17 May 2016 10:05] MySQL Verification Team 
Thank you for the bug report. Duplicate/related http://bugs.mysql.com/bug.php?id=79081.
[17 May 2016 12:22] qian wang 
yes, i found some duplicate bugs, 
and i've uninstalled and reinstall, 
i've tried 32 bits version, 
i've tried restart service mysql, 
i've tried create other connection.
but it dosen't work.

for they other duplicate bugs, they are not resolved neither
[17 May 2016 12:30] MySQL Verification Team 
The bug mentioned is in open status, please comment there anything you think is relevant. Thanks.
[17 May 2016 12:40] qian wang 
screenshot

Attachment: connect.PNG (image/png, text), 33.96 KiB.
[17 May 2016 12:40] qian wang 
error message

Attachment: error.PNG (image/png, text), 36.72 KiB.
[4 Sep 2017 6:32] Milos Milutinovic 
Similar thing happens to me with 6.3.8 version on Debian Stretch workstation. It worked fine before I had upgraded to Stretch, but now when I try to connect to a remote server over VPN connection it just freezes, the process is using 100% CPU until I kill it. I can connect to local server (running inside Docker container) and I can connect to a remote host over SSH.

The only difference is that my local database and then one I'm connecting to over SSH have several databases, while the one where I have this problem has several thousands of databases.

I see this in the log: https://pastebin.com/SW2PUXfQ