MySQL Error : MySQL server has gone away

[almqdad]

hello

some time last week I received email regarding moving my site to a new server

We have recently added several
new servers that boast an increase in speed, power, and stability. At this
this time we are excited to inform you that alhawza.net is
scheduled to be upgraded to one of these new servers; FREE of charge. Below
you will find important migration details.

thanks for blue host however from that date I am getting

MySQL Error : MySQL server has gone away

I opened a ticket on Mon Dec 31 2007 09:50AM

more than 5 days no respond

I tried life chat I get

MySQL:

Dear BlueHost Customer,

Due to the complex nature of trouble shooting MySQL database issues and to save time we ask that you contact our Customer Support team by phone or ticket center:

How To Contact Support:

(Phone Support) - Main Line: 888-401-4678 or Outside U.S: 801-765-9400

Sales Questions: Press 1

Support Questions: Press 2

Billing Questions: Press 3

Account Verifications: Press 4

(Help Center)- MySQL Knowledgebase Issues

(Support Forums)- Post Your Questions or Comments

(Ticket Center)- Submit a MySQL Support Ticket.(Please Allow 24-48 hours for a Response)


ticket Id is ID: 717551

some body at blue host need to increase msql timeout

thanks

[[metalremains]]

I have a different problem but I'm also waiting for a reply to my ticket since Jan 1st (#715384). So, yeah, you're not alone with this support problem.

[Early Out]

The ticket system has been something of a problem for a while now - they seem always to be many days behind. I always recommend using Live Chat, instead. Frankly, I'm a bit disappointed in the response that almqdad got on Live Chat - "...to save time?!" How does submitting a ticket save time?

Phoning might be a good idea, but for those outside the U.S., that's not a very attractive option, since there's no such thing as a toll-free call from outside the U.S.

[[metalremains]]

The ticket system has been something of a problem for a while now - they seem always to be many days behind. I always recommend using Live Chat, instead. Frankly, I'm a bit disappointed in the response that almqdad got on Live Chat - "...to save time?!" How does submitting a ticket save time?

Phoning might be a good idea, but for those outside the U.S., that's not a very attractive option, since there's no such thing as a toll-free call from outside the U.S.

I tried Live Chat, but I always get the same message as almqdad (been trying for a few days), and as I don't live in the US, I can't really phone them.

[markdevoll]

did you tell him you were not located in the united states and that opening a ticket hasnt helped?

[[metalremains]]

did you tell him you were not located in the united states and that opening a ticket hasnt helped?

I don't really got what you said, as that message appears when I try to enter the chat (it doesn't allow me to send any message or anything, it's just a page with that message, with no form).

[Early Out]

It sounds like they have a filter in place that automatically generates that message if you start out by asking anything about MySQL. Hook up to Live Chat, and in the initial message box, don't say anything about MySQL - just enter something like, "I'm not in the U.S., so I can't phone. I have a server problem." Then wait until you get a human being on the other end of the chat.

[arnb]

I use a standard PHP script for connecting to my site that has built in diagnosis of the connection error. Although the site reader is usually the recipient of the bad news, it does give them some way to attempt to deal with the issue.

It popped up about 2 days ago while I was testing due to the MySQL Server getting "stuck" with too many connections and I contacted BH.

I directed the BH rep to the page showing the error and was asked how are you getting that information you don't have a PHP connect error showing. I politely explained the standard PHP error processing simply gives away too much information, and my explanation was grudgingly accepted. However after talking with the tech folks the rep seemed somewhat perturbed that I would have the audacity to have a non-site person attempt to report an error and requested the directions be removed--they won't. Let's face it we site owners are not always available to call BH for help. MySql server errors happen, if BH refuses to help it's their issue. To their credit the problem was fixed in a few minutes.

I've posted my PHP code for anyone to use. It also shows you how to set UTF8 with a PHP constant before executing this code.
for example:
define("XXXXSite_UTF8", true); //Tell Mysql to connect as UTF8 collation
require_once(ConnectScript.php');


<?php
/*
Nov 11, 2007 add support for UTF8 connection
Nov 12, 2007 add additional information so viewer/reader can contact Bluehost
Nov 12, 2007 suppress the PHP error message
Nov 13, 2007 Fix text of XXXXsite_UTF8 constant to be correct all the time
Dec 21, 2007 Move definition of xKill_it after undefined xkill_it on a connect error
Dec 22, 2007 Update instructions to be more precise
*/
if (!function_exists('xKill_it'))
{
function xKill_it($reason)
{
echo "The host provider's database server for XXXX.ORG appears to be failing.<br><br>";
echo "<b>Please close your browser then retry this page.</b><br>Should the error persist for more than 5 minutes ";
echo "contact XXXX.ORG at (555) 555-1212 or email XXXX at XXXX.ORG<br><br>";
echo "Should you be unable to reach XXXX.ORG feel free to contact our host directly at (888) 401-4678<br>";
echo "Press 2 for technical support<br>";
echo "Tell the representative: MySql Box999 is failing for XXXX.Org along ";
echo "with the following error information.<br><br>";
die ($reason.mysql_error());
}
}

$link=@mysql_connect ("localhost", "xxxxxxxx_yyyyyyy", "zzzzzzzzzz")
or xKill_it("Could not connect: ");
@mysql_select_db("database_xx")
or xKill_it("Unable to select database: ");

//if (defined("XXXXSite_UTF8") && XXXXSite_UTF8) //wrong way to test! Nov 13, 2007
if (defined("XXXXSite_UTF8") && XXXXSite_UTF8===true) //switch to UTF8 if requested
{
@mysql_query("SET NAMES 'utf8'")
or xKill_it("Unable to set character set: ");
}
return;

?>

[Lee G]

I had the same problems start last night and its now annoying me with the constant error emails I keep getting

Sent a support ticket due to being a non US resident, waiting on the response

[arnb]

Sending email alerts on database connection issues can clog one's inbox since it is usually a Host issue. It was a conscious choice on my part to not use an email alert for this error.

Hope you get your problem resolved. Usually it's a simple MySql server reboot or finding the culprit connection(s).

[felgall]

Sent a support ticket due to being a non US resident, waiting on the response

BlueHost are very slow responding to support tickets. Try using Live Chat instead.