I got an installation that works online. Offline copies also worked until two weeks ago. Now the last try of a backup - I get about 10 feet length of database errors. They go away when I deactivate views via System table, so it is views causing trouble. When I re-activate Views, the same error is there. There is a lot of this:

user warning: MySQL server has gone away query: UPDATE cache_views SET data =

then it writes out the entire views cache which takes up most of the space ;)

and this

# user warning: MySQL server has gone away query: UNLOCK TABLES in F:\xampp\htdocs\Jobs\audioclassica-test\includes\database.mysql.inc on line 172.
# user warning: MySQL server has gone away query: SELECT data, created, headers, expire FROM cache_views WHERE cid = 'views_arguments:de' in F:\xampp\htdocs\Jobs\audioclassica-test\includes\database.mysql.inc on line 172.

and also this

Warning: MySQL server has gone away query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'php', 'MySQL server has gone away\nquery: UPDATE cache_views SET data =
but this i interpret he just wants to write error messages to watchdog table and doesn't succeed

Most of the other errors mention locales_source and locales_target, so maybe interaction with i18n (which I got also installed?)

I suspect there is something wrong with the views cache. I had trouble before when trying to import the database locally because views cache appeared to be erroneous. Can there be any relation to this issue? http://drupal.org/node/218187 cache_views is about 1MB in size.

I fear about my project, cause not being able to do a local backup - not good.

I thought about a workaround in exporting the existing views (it are not to many) and importing them in an older, working install. But there appear to be dependencies wider than that. I tried by not importing any table that has views_ in front of the name, but obviously this is not enough.

Comments

merlinofchaos’s picture

Status: Active » Closed (won't fix)

MySQL server has gone away

Views cannot be held responsible if MySQL crashes.

eigentor’s picture

Oh, holy Moly. Just increased allowed packet size for mysql, gone...
those precious hours of my life wasted worriyng... ;)
Thanks nevertheless.

davidwhthomas’s picture

Increasing the MySQL packet size in my.ini fixed it for me too:

my.ini
max_allowed_packet = 5M

marcrocs’s picture

AND if you happen to be using XAMPP with MySQL goto your my.conf file located C:\xampp\mysql\bin find the line that says "max_allowed_packet" and make it say "max_allowed_packet = 16M". That should do it.

This took me HOURS to find.

tbiscan’s picture

MANY PEOPLE ARE LOOKING FOR THIS SOLUTION!!!

GREAT!!!!!!!!!!!!!!!

Anonymous’s picture

Thanks very much for this helpful solution. I had this problem too - I am using xampp - and increasing the max_allowed_packet size in my.ini solved it.

Anonymous’s picture

My sincerest thanks to those who took the time to post here.
I used solution #4 specifically.