MySQL server has gone away?!?!

[dlewisr]

I've started receiving these emails over the last couple of days. The first email came after I used the auto back up mod manually, ready for a maintenance check. It was stuck in a loop. Then I noticed that when I ran the 'Rebuild Custom Avatar Thumbnails' on the General Update Tools, there was a note at the top saying 'Processing 439 (jpg). Is that the number of avatars I have or does that mean avatar 439 is corrupt? I ask because I have never noticed that before when I have used these toold.

I'm not sure if these two things are related as I am not at all savvy about these things.

This is the email I receive.

Database error in vBulletin 4.2.1:

Invalid SQL:

INSERT INTO cronlog
(varname, dateline, description, type)
VALUES
('cbu_crontask',
1374391680,
'Backup Completed Successfully',
0);

MySQL Error : MySQL server has gone away
Error Number : 2006
Request Date : Sunday, July 21st 2013 @ 08:28:00 AM
Error Date : Sunday, July 21st 2013 @ 08:56:16 AM
Script : http://**sitename***/cron.php?rand=1374391673
Referrer : http://***sitename***/search.php?searchid=167672
IP Address : 81.151.101.195
Username : Unregistered
Classname : vB_Database
MySQL Version :

The number below '('cbu_crontask', is always different except for the beginning 13743*****. Is my db corrupted and if so, how can I fix it,

Is it that avatar 439? If so how do I find an individual image. The avatar stats ay we don't have any Custom Avatars. I mention this as I've never noticed that before, although it could be that I'm a little more aware because I'm now actually looking for things.

Thanks in advance.

[betterthanyours]

Increase the wait_timeout to a higher value (if you have access to the .conf file)

[dlewisr]

Thanks for that info. I'm not sure if it is a time out, even though I say it's on a loop, as this happens within 15 secs and has never happened before. In saying that, your suggestion is a good idea. I take it that is the words that I look for in the config file 'wait_timeout. I'll try that now.

Thanks again.

--------------- Added [DATE]1374519234[/DATE] at [TIME]1374519234[/TIME] ---------------

I've looked at the config file and the only line I find with 'timeout' is this

$config['Misc']['memcachetimeout'][$i] = 1;

Then checking your post again I see that you have put .conf file. I take it I'm looking at the wrong file? Where would I find the file you mention?

[Lynne]

As already noted, it's a wait_timeout issue. I get the same on my server when I do backups because they are large and by the time the backup is finished and then the script wants to write to the cronlog table to say it did the task, the wait_timeout is over and done with and you get MySQL Server has Gone Away.

If you are getting that error because of other things on the site also, they I would worry about it. If it's just this daily backup script, I would remove the line in the script that logs the action and then the errors will stop.

[Zachery]

Its a MySQL server thing, not a vBulletin setting.

[dlewisr]

Thanks for your responses Lynn and Zachery. No surprise that it was something that I had caused myself. I had changed the settings of the auto back up and set the button for 'Block Processing' to no. As you already mentioned, this created the time out issue.

Thanks again.

[mad4social]

Is there anyone that knows the exact command for edit php.ini by root?

[nxtgen]

sudo nano php.ini

I have the same issue when I try to access my blogs. As soon as you attempt to open a blog, the site times out and i receive a similar message via email

[Zachery]

Its not a php thing, but you should really not hijack others topics.

[ForceHSS]

http://www.mysql.com/doc/G/o/Gone_away.html
http://www.mysql.com/doc/C/o/Common_errors.html
http://www.mysql.com/doc/S/e/Server_parameters.html
http://www.mysql.com/doc/O/p/Option_files.html
http://www.mysql.com/doc/S/H/SHOW_VARIABLES.html

The most common reason for the MySQL server has gone away error

1. Is that the server timed out and closed the connection. By default, the server closes the connection after 8 hours or 28800 seconds if nothing has happened. You can change the time limit by setting the wait_timeout variable when you start mysqld via your server's /etc/my.cnf as well.

2. Another common reason to receive the MySQL server has gone away error is because you have issued a ``close'' on your MySQL connection and then tried to run a query on the closed connection. You can check that the MySQL hasn't died by executing mysqladmin version and examining the uptime.

i.e. to check mysql uptime, in shell as root user type:

mysqladmin -u root -p version

3. You can also get these errors if you send a query to the server that is incorrect or too large. If mysqld gets a packet that is too large or out of order, it assumes that something has gone wrong with the client and closes the connection. If you need big queries (for example, if you are working with big BLOB columns), you can increase the query limit by starting mysqld with the -O max_allowed_packet=# option (default 1M) or via max_allowed_packet variable in your /etc/my.cnf file and restarting mysql after you edited your /etc/my.cnf file. The extra memory is allocated on demand, so mysqld will use more memory only when you issue a big query or when mysqld must return a big result row

4. or simply your host restarted mysql.. i'd contact your web host