My local site is down with the following error. I've searched issues and forum and tried the suggested fixes to similar issues (upping mysql max_allowed_packet = 16M, running update.php repeatedly) and I also tried clearing cache tables and manually disabling the last few installed modules via phpmyadmin. After clearing browser cache I am able to access the site as an anonymous user, but as soon as I log in mysql goes away and I get the error again.

Nothing has worked and now at a dead end and not sure what to try next to get it back up and running.

Additional uncaught exception thrown while handling exception.

Original

PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: DELETE FROM {cache} WHERE (cid LIKE :db_condition_placeholder_0 ESCAPE '\\') ; Array ( [:db_condition_placeholder_0] => entity\_info:% ) in cache_clear_all() (line 176 of D:\www\projects\construct3d\drupal7-master\includes\cache.inc).

Additional

PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: SELECT b.* FROM {block} b WHERE (b.theme = :db_condition_placeholder_0) AND (b.status = :db_condition_placeholder_1) ORDER BY b.region ASC, b.weight ASC, b.module ASC; Array ( [:db_condition_placeholder_0] => default_site [:db_condition_placeholder_1] => 1 ) in _block_load_blocks() (line 727 of D:\www\projects\construct3d\drupal7-master\modules\block\block.module).

Uncaught exception thrown in session handler.

PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away in _drupal_session_write() (line 209 of D:\www\projects\construct3d\drupal7-master\includes\session.inc).

Uncaught exception thrown in shutdown function.

PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: DELETE FROM {semaphore} WHERE (value = :db_condition_placeholder_0) ; Array ( [:db_condition_placeholder_0] => 8193656144fb88c50335041.03538706 ) in lock_release_all() (line 269 of D:\www\projects\construct3d\drupal7-master\includes\lock.inc).

Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[HY000]: General error: 2006 MySQL server has gone away' in D:\www\projects\construct3d\drupal7-master\includes\database\database.inc:2136 Stack trace: #0 D:\www\projects\construct3d\drupal7-master\includes\database\database.inc(2136): PDOStatement->execute(Array) #1 D:\www\projects\construct3d\drupal7-master\includes\database\database.inc(664): DatabaseStatementBase->execute(Array, Array) #2 D:\www\projects\construct3d\drupal7-master\includes\database\database.inc(2315): DatabaseConnection->query('SELECT expire, ...', Array, Array) #3 D:\www\projects\construct3d\drupal7-master\includes\lock.inc(167): db_query('SELECT expire, ...', Array) #4 D:\www\projects\construct3d\drupal7-master\includes\lock.inc(146): lock_may_be_available('schema:runtime:...') #5 D:\www\projects\construct3d\drupal7-master\includes\bootstrap.inc(405): lock_acquire('schema:runtime:...') #6 D:\www\projects\construct3d\drupal7-master\includes\bootstrap.inc(427): DrupalCacheArray->set( in D:\www\projects\construct3d\drupal7-master\includes\database\database.inc on line 2136

Sorry, this is a forum repost (see http://drupal.org/node/1590308) as I felt that wasn't the right place for it.

Comments

inteja’s picture

inteja commented

Anyone got any ideas?

cweagans’s picture

cweagans
He/Him
Primary language English
Location Boise, ID, USA
commented
Priority: Major » Normal

Support requests are neither major nor critical.

inteja’s picture

inteja commented

Well, it's major and critical to me because my site has been vaporized for no clearly apparent reason, which I thought might also be of major concern to others who may run across this strange issue in future.

If indeed those priorities aren't valid options for support requests, maybe it would be better to conditionally set the priority options based on chosen category.

cweagans’s picture

cweagans
He/Him
Primary language English
Location Boise, ID, USA
commented

Please see http://drupal.org/node/45111 regarding the appropriate issue priority, especially the bottom paragraph.

This is not a bug with Drupal and appears to be related to your MySQL configuration. I would suggest bumping the max_allowed_packet up to something like 32M or even 64M. Also of interest is your key_buffer_size: bumping that up may help as well.

It's basically a matter of having too much going on in your Drupal site for your MySQL configuration. Give your DB more resources and the problem will go away.

inteja’s picture

inteja commented

Thanks. Will try upping key_buffer_size (have already tried extremely high max_allowed_packet with no change).

inteja’s picture

inteja commented

Now have both max_allowed_packet and key_buffer_size = 1024M and have tried various values from 64M up.

Still no joy.

cweagans’s picture

cweagans
He/Him
Primary language English
Location Boise, ID, USA
commented
Status: Active » Closed (won't fix)

Well, here's the manual page: http://dev.mysql.com/doc/refman/5.1/en/gone-away.html

Sorry, but this is not a Drupal issue - it's a MySQL configuration issue.