MySQL Bugs: #52332: Cannot make a connection

Bug #52332	Cannot make a connection
Submitted:	24 Mar 2010 14:30	Modified:	1 May 2010 15:47
Reporter:	Harold Frayman	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.16 R 5249	OS:	MacOS (10.5.8 (9L31a) Intel)
Assigned to:		CPU Architecture:	Any

Description:
From a managed machine attempting to connect, or create a new connection, the password is not saved in the keychain (this is not a problem for any other application). When the password is entered manually the dialog reappears once and then closes. The error mesasage is (for example): "Cannot Connect to Database Server//Your connection attempt failed for user 'esd' from your host to server at oddjob:3306:  Access denied for user 'esd'@'10.124.73.59' (using password: NO)" (see log extract below).

The same behaviour occurs with a connection to the local host, however defined.

I have no problem connecting from the commandline (mysql -uesd -p -hoddjob).

It makes no difference if a schema is named or not.

Other operations (eg opening an existing mwb) are, as far as I can tell, fine.

This behaviour is new compared with 5.1.

24/03/2010 14:22:20 [0x0-0x9a09a0].com.sun.MySQLWorkbench[50100] ** (process:50100): WARNING **: :0: link 'com.mysql.wb.menu.view.advanced' <object app.MenuItem> key=owner could not be resolved 
24/03/2010 14:22:20 [0x0-0x9a09a0].com.sun.MySQLWorkbench[50100] ** (process:50100): WARNING **: :0: link '44768D0F-4838-40DA-9FAC-DB98D0B08E49' <object GrtObject> key=owner could not be resolved 
24/03/2010 14:22:20 [0x0-0x9a09a0].com.sun.MySQLWorkbench[50100] ** (process:50100): WARNING **: :0: link '44768D0F-4838-40DA-9FAC-DB98D0B08E49' <object GrtObject> key=owner could not be resolved 
24/03/2010 14:22:51 [0x0-0x9a09a0].com.sun.MySQLWorkbench[50100] ** (process:50100): WARNING **: /var/folders/zU/zU3FfUpZHzSbUO7iETNHH+++1y2/-Tmp-//gup.mwbd/document.mwb.xml:0: link 'EE329625-C00B-4D9E-BAFD-BAB1455AACEC' <object > key= could not be resolved 
24/03/2010 14:22:51 [0x0-0x9a09a0].com.sun.MySQLWorkbench[50100] ** (process:50100): WARNING **: skipping element 'link' in unserialized document, line 0 
24/03/2010 14:22:51 [0x0-0x9a09a0].com.sun.MySQLWorkbench[50100] ** (process:50100): WARNING **: /var/folders/zU/zU3FfUpZHzSbUO7iETNHH+++1y2/-Tmp-//gup.mwbd/document.mwb.xml:0: link '496D99D2-312D-4145-B35F-0C038721795A' <object GrtObject> key=owner could not be resolved 
24/03/2010 14:23:16 MySQLWorkbench[50100] opening plugin bundle /Applications/MySQLWorkbench.app/Contents/PlugIns/db.mysql.editors.mwbplugin ([DbMysqlTableEditor initWithModule:GRTManager:arguments:...]) 
24/03/2010 14:23:35 [0x0-0x9a09a0].com.sun.MySQLWorkbench[50100] ** Message: unhandled message 4: db.mysql.plugin.sync.db finished in 0.00s 

How to repeat:
In Workbench 5.2.16, attempt to use any facility that needs a connection

Looks like a duplicate of bug #51673. Please, check.

Does look like oa duplicate of Bug #51673 (sorry, didn't see that when I searched), but I can't get localhost either. I will try the IP-address-then-hostname workaround tomorrow

Please, inform us if this workaround helps.

I have now tested the workround (first supplying an IP address) and it does not work. I cannot connect either to the remote server or local host using IPv4 addresses.

I have also tested the same wb version from an unmanaged machine connected by VPN and there are no problems at all connecting to exactly the same server with the same settings. Which feels a bit like firewall, but that would imply that wb52 is using a different port from the one used by wb51 and the default command line. 

Harold Frayman

Are you really sure that the server is listening on the port?
Are you really sure that no firewall is blocking?

I am sure that the connection works -- on 3306 -- from outside the firewall via VPN and from within the firewall using a terminal connection. I am no firewall expert, but I cannot see how a rule could exclude a particular machine on a particular port depending on the means by which it connects, nor can I easily believe that the rules allow machines it knows nothing about (except that it is outside the firewall, because it is using a VPN tunnel to get in) but refuses machines it recognises inside the firewall.

Stored connection from Workbench 5.1 aren't working with Workbench 5.2.

This is a known issue.

You told in a side sentence that you used the connection settings from WB 5.1.

Please try it with a fresh (new) configuration that you create on Workbench 5.2.

In fact I started off with new connections in 5.2 but cannot save the password in the keychain. Nor can I connect when I present the unstored password. If I Test Connection, the error message is "Access denied ... using password NO" even though I have just re-entered it, whether I check the 'Save password...' box or not

Your last comment looks even more similar to bug #51673. I'd consider this a duplicate.

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