Never seen this error

[Bluemax]

Gents I have four sites on two servers, never had an install issue until going for my fifth. I run the installer, but the Check database connection does nothing, so if I go to Next, I get this error. I have changed the database twice and replaced the whole installation twice, still get this error. I would appreciate any help with this.

Installing the tables...

Fatal error: Uncaught <blockquote><font face=arial size=2 color=000099><b>Last Error --</b> [<font color=000000><b>Lost connection to MySQL server at 'reading initial communication packet', system error: 111 (2013)</b></font>]<br />[<font color=000000><b></b></font>]</font><p> </blockquote><hr noshade color=dddddd size=1> thrown in /hermes/bosweb/web121/b1216/ipg.americavaus/paav/core/classes/ezdb/ezdb_mysql.class.php on line 99

[solved]

[Kyle]

I'm guessing it's an issue with the remote or local SQL host, I think.

I'm not sure, but that's what it looks like.

[simpilot]

I am not sure if this is a new server you are using versus the other two you already have set up but it looks like a server/hosting side issue. The offical MySql definition for that error code is:

There are three likely causes for this error message.

Usually it indicates network connectivity trouble and you should check the condition of your network if this error occurs frequently. If the error message includes “during query,” this is probably the case you are experiencing.

Sometimes the “during query” form happens when millions of rows are being sent as part of one or more queries. If you know that this is happening, you should try increasing net_read_timeout from its default of 30 seconds to 60 seconds or longer, sufficient for the data transfer to complete.

More rarely, it can happen when the client is attempting the initial connection to the server. In this case, if your connect_timeout value is set to only a few seconds, you may be able to resolve the problem by increasing it to ten seconds, perhaps more if you have a very long distance or slow connection. You can determine whether you are experiencing this more uncommon cause by using SHOW GLOBAL STATUS LIKE 'Aborted_connects'. It will increase by one for each initial connection attempt that the server aborts. You may see “reading authorization packet” as part of the error message; if so, that also suggests that this is the solution that you need.

If the cause is none of those just described, you may be experiencing a problem with BLOB values that are larger than max_allowed_packet, which can cause this error with some clients. Sometime you may see “packet too large” as part of the error message, and that confirms that you need to increase max_allowed_packet.

My guess is that you are on a shared hosting environment and the database is being taxed to it's limit, but in any event I would start a support ticket with your host's support group.