MySQL Bugs: #66729: open connection to start querying failed with error "cannot connect to database

Bug #66729	open connection to start querying failed with error "cannot connect to database
Submitted:	7 Sep 2012 10:07	Modified:	29 Oct 2012 16:24
Reporter:	Stefan Pietsch	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.42	OS:	Windows (Microsoft Windows 7 Service Pack 1 (build 7601), 64-bit)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
Connections with command line tools or workbench server administration are possible. Only connections with workbench sql development module do not work.

----- Developer Notes -----

MySQL Workbench CE for Windows version 5.2.42  revision 9752
Configuration Directory: C:\Users\stefan.MULTICHART\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
OS: Microsoft Windows 7  Service Pack 1 (build 7601), 64-bit
CPU: 4x Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz, 3.8 GiB RAM
Active video adapter (1): NVIDIA GeForce GT 640M           
Installed video RAM: 1024 MB
Current video mode: 1366 x 768 x 4294967296 Farben
Used bit depth: 32
Driver version: 8.17.12.9616
Installed display drivers: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Current user language: Deutsch (Deutschland)

How to repeat:
All times, I try to connect, the error occured.

Can you paste the full error text?

Workbench log with error message at the end of the file.

Attachment: wb.log (application/octet-stream, text), 11.84 KiB.

I paste the workbench logfiles with the complete error message at the end of the file, but I think, there are no more detailed information.

Is it possible to get more detailed information? Can I increase the loglevel?

Please try version 5.2.44. Thanks.

I've installed version 5.2.44, but the same problem occurs.
Is it possible to increase the loglevel?

Hello Stefan.
Can you please run in your MySQL command line client the following command and paste here the results?
mysql> status;
--------------
mysql  Ver 14.14 Distrib 5.5.16, for Win32 (x86)

Connection id:          45
Current database:
Current user:           root@localhost
SSL:                    Not in use
Using delimiter:        ;
Server version:         5.5.28 MySQL Community Server (GPL)
Protocol version:       10
Connection:             localhost via TCP/IP
Server characterset:    utf8
Db     characterset:    utf8
Client characterset:    cp850
Conn.  characterset:    cp850
TCP port:               3306
Uptime:                 5 hours 8 min 45 sec

Threads: 1  Questions: 7052  Slow queries: 0  Opens: 311  Flush tables: 1  Open
tables: 0  Queries per second avg: 0.380
--------------
Thanks.

Hello Armando,

I don't know what happened. Today I came back from holiday and wanted to create the desired status output. Before I tried to get a connection from workbench once more and all worked well.

All connections to the six available servers now work well. Before my holiday, no connection had worked.

Below you find the "status" of one of the server.

--------------
mysql  Ver 14.14 Distrib 5.5.27, for Win64 (x86)

Connection id:          247
Current database:
Current user:           root@stefannb6.multichart.de
SSL:                    Not in use
Using delimiter:        ;
Server version:         5.5.13 MySQL Community Server (GPL)
Protocol version:       10
Connection:             beate3 via TCP/IP
Server characterset:    latin1
Db     characterset:    latin1
Client characterset:    utf8
Conn.  characterset:    utf8
TCP port:               3306
Uptime:                 27 days 21 hours 7 min 39 sec

Threads: 2  Questions: 197097754  Slow queries: 80  Opens: 1530  Flush tables: 1  Open tables: 5  Queries per second avg: 81.822
--------------

I don't know what we can do but I think we can close this bug.

Thanks.

Great news Stefan, please do not hesitate in re-opening this bug if you can reproduce this issue again.
Thanks.