Bug #1666 Control Center crash on max _connect_errors exceeded
Submitted: 26 Oct 2003 6:47 Modified: 19 Nov 2003 7:19
Reporter: Alistair Maclean Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQLCC Severity:S3 (Non-critical)
Version:0.9.2beta OS:Microsoft Windows (Win2K)
Assigned to: Bugs System CPU Architecture:Any

[26 Oct 2003 6:47] Alistair Maclean
Description:
Connecting to a server that has blocked access to the computer running control center because of max_connnect_errors exceeded, the CC application will crash. 

How to repeat:
Repeat this the required number of times to exceed the connect error count:
D:\mysql\bin>mysql -u bogususer -p -h servername -D mysql

Enter Control Center.
If the connection already exists, delete it.
Create a new connection to the remote mysql server
Give valid db instance name, server name and logon credentials

system gives error:
The instruction at "0x39ee1141" referenced memory at "0x00000156". The memory could not be "read". (Ok and Cancel buttons) 
Click OK, Control Center is unloaded.

To clear the error and recreate a connection requires access to the remote server and foing the "mysqladmin flush-hosts" command. This message, is I believe, in the error message given to the client on connection failure.

Suggested fix:
error check connection, more graceful failure on connection not being made.
[19 Nov 2003 7:19] MySQL Verification Team
Yes it is a known bug which makes MySQLCC crash when isn't possible
to connect with server for several reasons.