Bug #1829 Weird failure to connect to the MySQL database
Submitted: 13 Nov 2003 7:15 Modified: 13 Nov 2003 8:00
Reporter: Robin Fredman Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:4.0.16 OS:Windows (Win98)
Assigned to: CPU Architecture:Any

[13 Nov 2003 7:15] Robin Fredman
I have a webpage which is powered by Apache 1.3.29, PHP 4.3.3 and MySQL 4.0.16. The whole website is displayed in PHP, and uses a MySQL Database to retrieve the information. The problem surfaces after the site has been running a while, and most often when I have been using my computer to surf the net/ran some taxing applications on it. What happens is that suddenly, the MySQL database is unreachable, as if it crashed, the following text is displayed in the webbrowser:

Warning: mysql_connect(): Can't connect to MySQL server on 'localhost' (10055) in E:\Program\Apache Group\Apache2\htdocs\functions\dbconnect.php on line 2 
Could not connect to localhost 

It is as if the server suddenly becomes unrechable, the error is exactly the same as if there were not server running at all. However, if you use 'Mysqladmin version' it sometimes fails to connect, but usually is able to display the server as running. 'Mysqladmin reload' solves the problem temporarily (usually 5 minutes approximately), and likewise fails to connect at the first or second try, but is then succesful.

Worth to note is that I am a temporary host, and that the webserver ran flawlessly on Win2k with MySQL version 4.0.10.

Also, a reboot solves the problem for a while, but it recurs. I am also running it all from the drive E: .

How to repeat:
I have no idea really. It's a win98 server, uses MySQL for storing information and code, and php for displaying it.

Perhaps it's some kind of flooding-error?
[13 Nov 2003 8:00] Dean Ellis
This would appear to be either a problem with the way your application is using MySQL or purely a Windows 98 configuration issue (increasing the number of allowed open TCP sockets for instance), and not a bug in MySQL.

You can find suggestions for addressing it via Microsoft's knowledge base (or Google).

Thank you.