Bug #582 mysqladmin fails to connect to server since 4.0 upgrade
Submitted: 4 Jun 2003 3:35 Modified: 30 Jul 2003 23:07
Reporter: Dave Torr Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:4.0 OS:Windows (Windows ME)
Assigned to: CPU Architecture:Any

[4 Jun 2003 3:35] Dave Torr
Description:
Since upgrading from 3.23 I have a problem with all command line utils such as mysqladmin and mysql, which used to work fine. Whenever I run them I get the messages

C:\MYSQL\BIN\MYSQLA~1.EXE: connect to server at 'localhost' failed
error: 'Can't connect to MySQL server on 'localhost' (10050)'
Check that mysqld is running on localhost and that the port is 3306.
You can check this by doing 'telnet localhost 3306'

The telnet works. My application (using VB6) still works and MyTool also works fine. I have tried various combinations of username and password but always seem to get the same response. 

Main problem is I can no longer close the server down so I have to kill it which I guess risks data corruption

How to repeat:
Install standard system under ME and try the tools. I can supply the my.ini file and the username database if that will help at all
[5 Jun 2003 4:15] MySQL Verification Team
Please try:

mysql -uroot

mysqladmin shutdown -uroot 

If the above works, please read the bug #464 how to set the user privileges
in the version 4.0.XX.
[5 Jun 2003 17:39] Dave Torr
Thanks - still fails.
The mysql command gives Error 2003 Can't connect to server on localhost (10050) and the mysqladnmin gives error as reported in original bug.

Don't know if it is relevant at all but my application (written in VB6) works fine if run from within the VB development environment but if compiled as an exe also fails to connect - and it used to work on 3.23
[30 Jul 2003 22:16] Dave Torr
I think the issue is solved. I used to use ZoneAlarm but as this slowed down the communication between the server and application - and since my development machine is no longer on-line - I disabled it. 

Today I thought I would re-enable it to at least see if the clients were trying to connect to the server and discovered that with ZoneAlarm enabled they worked - if I disabled it (when in theory it should allow all traffic) only some things worked as I said before. Finally I uninstalled it and everything is OK - seems like even when disabled it had some influence - maybe through a DLL or something?