MySQL server has gone away

Perhaps this might help? At least give you a starting point...

http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

----------------
Dominic Ryan
www.iis-aid.com

This was happening to me with lighty 1.4.13. This is the version that was listed as most up to date when doing an apt-get install on ubuntu. The newest version (1.4.18) appears to fix the problem (but you must download and install it yourself):

http://www.lighttpd.net/2007/9/9/1-4-18-speeding-up-a-bit

Some people were kind enough to toss some .deb files on that page.

Hello,

I had the same problem, i finally understood that my drupal install was getting too big, and it needed some mysql tweaking. Here is the solution that worked for me:

http://drupal.org/node/186384#comment-284542

MySql : "Warning: MySQL server has gone away" - Tune MySql to resolve this problem

I am using MySQL 5 with persistent connections between the web server and the database server.

I had the same problem: "MySQL server has gone away" and increasing max_allowed_packet variable did not fix anything.

This problem happened after very long scripts which actually exceeded MySQL wait_timeout variable.

One solution could have been to increase wait_timeout. My problem was that wait_timeout is also used to close persistent connection after a long inactivity. I did not want to keep such connections opened if they were unused.

So I tried to detect such failure and manually reconnect the web server to the database.

My changes:

• includes/database.inc

/**
 * Activate a database for future queries.
 *
 * If it is necessary to use external databases in a project, this function can
 * be used to change where database queries are sent. If the database has not
 * yet been used, it is initialized using the URL specified for that name in
 * Drupal's configuration file. If this name is not defined, a duplicate of the
 * default connection is made instead.
 *
 * Be sure to change the connection back to the default when done with custom
 * code.
 *
 * @param $name
 *   The name assigned to the newly active database connection. If omitted, the
 *   default connection will be made active.
 *
 * @return the name of the previously active database or FALSE if non was found.
 */

/* Replacement of:
function db_set_active($name = 'default', $reset = 0) {
by: */
function db_set_active($name = 'default') {

  global $db_url, $db_type, $active_db;
  static $db_conns;

// Add of:
  if ( $reset == 1 ) {
    $key = array_search($active_db, $db_conns, TRUE);
    if ( $key !== FALSE ) {
      $name = $key;
      unset($db_conns[$name]);
    }
  }

  if (!isset($db_conns[$name]) || $reset == 1) {
    // Initiate a new connection, using the named DB URL specified.
    if (is_array($db_url)) {
      $connect_url = array_key_exists($name, $db_url) ? $db_url[$name] : $db_url['default'];
    }
    else {
      $connect_url = $db_url;
    }

    $db_type = substr($connect_url, 0, strpos($connect_url, '://'));
    $handler = "./includes/database.$db_type.inc";

    if (is_file($handler)) {
      include_once $handler;
    }
    else {
      drupal_maintenance_theme();
      drupal_set_title('Unsupported database type');
      print theme('maintenance_page', '<p>The database type '. theme('placeholder', $db_type) .' is unsupported. Please use either <var>mysql</var> for MySQL 3.x &amp; 4.0.x databases, <var>mysqli</var> for MySQL 4.1.x+ databases, or <var>pgsql</var> for PostgreSQL databases. The database information is in your settings.php file.</p>
<p>For more help, see the <a href="http://drupal.org/node/258">Installation and upgrading handbook</a>. If you are unsure what these terms mean you should probably contact your hosting provider.</p>');
      exit;
    }

    $db_conns[$name] = db_connect($connect_url);
  }

  $previous_db = $active_db;
  // Set the active connection.
  $active_db = $db_conns[$name];

  return array_search($previous_db, $db_conns);
}

• includes/database.mysql.inc

/**
 * Helper function for db_query().
 */

/* Replacement of:
function _db_query($query, $debug = 0, $attempt=0) {
by: */
function _db_query($query, $debug = 0) {

  global $active_db, $queries;

  if (variable_get('dev_query', 0)) {
    list($usec, $sec) = explode(' ', microtime());
    $timer = (float)$usec + (float)$sec;
  }

  $result = mysql_query($query, $active_db);

  if (variable_get('dev_query', 0)) {
    $bt = debug_backtrace();
    $query = $bt[2]['function'] . "\n" . $query;
    list($usec, $sec) = explode(' ', microtime());
    $stop = (float)$usec + (float)$sec;
    $diff = $stop - $timer;
    $queries[] = array($query, $diff);
  }

  if ($debug) {
    print '<p>query: '. $query .'<br />error:'. mysql_error($active_db) .'</p>';
  }

  if (!mysql_errno($active_db)) {
    return $result;
  }
  else {

// Add of:
    if ( $attempt == 0 ) {
      db_set_active('unused', 1);
      return _db_query($query, $debug, 1);
    }

    trigger_error(check_plain(mysql_error($active_db) ."\nquery: ". $query), E_USER_WARNING);
    return FALSE;
  }
}

Could I have your opinion about this?

Sylvain

I'm having the same problem on my freshly developed D6 site - no active users yet!!

Found this bit online:

IF you have an access to php.ini you can add this line :
mysqli.reconnect = On

From what I've read, sounds like this should solve the issue... I know this error will go away if I refresh enough times... but that's unacceptable! And I'm afraid this will only get worse when more users sign on...

However, I don't have access to the php.ini file as I'm on a shared hosting plan. So I was wondering if there's a way to override it? Like on Drupal's settings.php page, you could increase PHP's memory limit by adding:

ini_set('memory_limit', '96M');

So, can we add "mysqli.reconnect = On" to the settings.php file too?

try db_tweaks module

Any more detail update on it ??? please share ...

I had a similar problem and couldn't find the problem. The problem was there when I wasn't logged in (anonymous), but when I was logged in (admin), the problem was no longer there. The only difference was the (re)captcha module, so I turned it off. The problem was gone, but now I had to find a new captcha modules >> I'm going to try Mollom.

Spent several hours with this problem and eventually switched off update status module and the problem went away

Lee

I installed the DB Maintenance module and optimzied all the cache tables. This resolved the problem for me.

Subscribing; have the same error on D7 and cannot create new content (new panel specifically).

Tried disabling update module, making changes in the MySQL config (up to 64MB) but still no solution.

[EDIT]

Seems that token + entity tokens were taking too much resources. I have about a dozen of content types with many fields so the token accordion was pretty long. I disabled the metatag module and it worked again.

Drupal 7 had a bug that left DB connections open. Next release 7.18 will have a fix for this. http://drupal.org/node/843114