Modify ↓
Opened 18 years ago
Closed 18 years ago
#3900 closed defect (duplicate)
MySQL server has gone away
Reported by: | anonymous | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | 0.10 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I get this traceback even though the MySQL server is happy. The only recourse is to restart the trac server. Maybe it is some kind of connection caching? It should be possible to catch this and reconnect. There is also a MySQL auto reconnect option, although I have never used it. Thanks!
Python Traceback Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 366, in dispatch_request dispatcher.dispatch(req) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 191, in dispatch req.authname = self.authenticate(req) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 149, in authenticate authname = authenticator.authenticate(req) File "/usr/lib/python2.4/site-packages/trac/web/auth.py", line 64, in authenticate authname = self._get_name_for_cookie(req, req.incookie['trac_auth']) File "/usr/lib/python2.4/site-packages/trac/web/auth.py", line 169, in _get_name_for_cookie (cookie.value, req.remote_addr)) File "/usr/lib/python2.4/site-packages/trac/db/util.py", line 47, in execute return self.cursor.execute(sql_escape_percent(sql), args) File "/usr/lib/python2.4/site-packages/trac/db/util.py", line 47, in execute return self.cursor.execute(sql_escape_percent(sql), args) File "/usr/lib/python2.4/site-packages/MySQLdb/cursors.py", line 163, in execute self.errorhandler(self, exc, value) File "/usr/lib/python2.4/site-packages/MySQLdb/connections.py", line 35, in defaulterrorhandler raise errorclass, errorvalue OperationalError: (2006, 'MySQL server has gone away')
Attachments (0)
Note:
See TracTickets
for help on using tickets.
See #3645.