OperationalError: (2006, 'MySQL server has gone away')

[Petteri Räty]

Traceback (most recent call last):
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 356, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 224, in dispatch
    resp = chosen_handler.process_request(req)
  File "/home/areijonen/trunk/lompsutin-plugin/lompsutin/LomaModule.py", line 72, in process_request
    user_id = lompsuttaja.getKayttajaId(req.authname)
  File "/home/areijonen/trunk/lompsutin-plugin/lompsutin/Lompsuttaja.py", line 29, in getKayttajaId
    user = User.hae('WHERE user_name="'+user_name+'"')
  File "/home/areijonen/trunk/lompsutin-plugin/lompsutin/DBTable.py", line 180, in hae
    cursor.execute(querystring)
  File "/usr/local/lib/python2.4/site-packages/trac/db/util.py", line 48, in execute
    return self.cursor.execute(sql)
  File "/usr/local/lib/python2.4/site-packages/trac/db/util.py", line 48, in execute
    return self.cursor.execute(sql)
  File "/usr/local/lib/python2.4/site-packages/MySQLdb/cursors.py", line 163, in execute
    self.errorhandler(self, exc, value)
  File "/usr/local/lib/python2.4/site-packages/MySQLdb/connections.py", line 35, in defaulterrorhandler
    raise errorclass, errorvalue
OperationalError: (2006, 'MySQL server has gone away')

This usually happens when I get back in the morning. Probably would be best for the trac Database Management code to handle these situations or the pool is not that useful.

[anonymous]

Duplicate of #3645

[Christian Boos]

I'll update 0.10.1 later this morning with the fixed pool code.

As it's a duplicate of #3645, I'll make a note there when the update is done.