Comments on: “MySQL server has gone away” Part 1: max_allowed_packet.

By: Mysql has gone away – General error: 2006 MySQL server has gone away – Magento | Spletni sistemi - Internetne rešitve in sistemske integracije

Fri, 03 Feb 2012 14:59:45 +0000

[...] WebYog blog post #1 [...]

By: Andrew

Andrew — Fri, 19 Aug 2011 07:58:45 +0000

Thanks.It saves my time.i have tried for last 2 days at last i have set
set global max_allowed_packet=1000000000;
set global net_buffer_length=1000000;

Thanks again

By: Karthik

Karthik — Thu, 05 Aug 2010 11:27:50 +0000

I also encountered the same issue and finally got it fixed by increasing “max_allowed_packet” setting..

Thanks.

By: Matthew Tommasi

Matthew Tommasi — Mon, 02 Aug 2010 04:04:01 +0000

I also encountered this error and have written up a step-by-step post on how to resolve it http://thesocialmediaguide.com.au/2010/07/31/solution-for-wordpress-database-error-mysql-server-has-gone-away-for-query/

By: jamie

jamie — Wed, 05 May 2010 02:03:04 +0000

I think max_allowed_packet is a con to be honest. I’ve tried changing it, restarting both Apache and MySQL and I STILL get the same problem – Mysql gone away.

Despite changing almost every upload related limit number (most being 8M or 10M) not even going up to 32M will let me upload a 1.4M jpg to store in a blob.

I can’t find anyone else on google with this same problem so I’m going to assume that the space-gods have just decided to stand in my way again..

By: peter_laursen

peter_laursen — Wed, 14 Apr 2010 04:38:53 +0000

more here:
http://bugs.mysql.com/bug.php?id=52802

By: junk1958

junk1958 — Tue, 29 Dec 2009 19:57:47 +0000

I ran into this same error message (“MySQL server has gone away”) which I agree is not only cryptic, but extremely useless.

After some Internet research and experimentation I found the error message “went away” after I set the following value in my.ini:
max_allowed_packet=12M

Unfortunately, I did not run across this blog article until after that configuration was tested. If what is said about the other max size is true, I suspect it should actually be 16M instead of 12M to overcome all future issues, so I will set that today before our new deployment. Thanks for the article.

By: :)

:) — Thu, 08 Oct 2009 00:59:39 +0000

Thank goodness this is the first google result. In no time, I realized I just had to shorten the 1000000+char queries to be able to import my backups with sqlyog.

And Notepad++ really helped. Thanks!

By: Webyog » “MySQL server has gone away” Part 2: session timeout.

Webyog » “MySQL server has gone away” Part 2: session timeout. — Wed, 02 Sep 2009 07:57:32 +0000

[...] small series on reasons for the error message: “MySQL server has gone away”. The first appeared here describing that “if a client sends a SQL-statement longer than the server max_allowed_packet [...]

By: peter_laursen

peter_laursen — Fri, 28 Aug 2009 12:38:25 +0000

@balu

I think it may depend on server version. After the latest patches has been included I understand that ‘max_allowed_packet’ will have to be defined as a startup parameter (typically in configuration file). I tried

SHOW VARIABLES LIKE ‘max_allowed_packet’; — 1048576
SET GLOBAL max_allowed_packet = 20000000; — approx = 20M
SHOW VARIABLES LIKE ‘max_allowed_packet’; — 1048576

This is 5.1.37 and it still may not have the latest patches. I think server will return an error with the patches. Also if it works for you currently to SET GLOBAL it will not work for users that do not have SUPER privilege (and it should not either of course).

I have no comment to ‘net_buffer_length’. I would have to study it first!