On 4/27/11 4:07 AM, Chris Withers wrote: > Hi Shane, > > Attempting to view the /manage_change_history_page of a history-keeping > relstorage is giving me: > > script statement failed: '\n SELECT 1 FROM current_object WHERE > zoid = %(oid)s\n '; parameters: {'oid': 1163686} > > ...and then: > > Traceback (innermost last): > Module ZPublisher.Publish, line 127, in publish > Module ZPublisher.mapply, line 77, in mapply > Module ZPublisher.Publish, line 47, in call_object > Module Shared.DC.Scripts.Bindings, line 324, in __call__ > Module Shared.DC.Scripts.Bindings, line 361, in _bindAndExec > Module App.special_dtml, line 185, in _exec > Module OFS.History, line 120, in manage_change_history > Module relstorage.storage, line 1011, in history > Module relstorage.adapters.dbiter, line 120, in iter_object_history > Module relstorage.adapters.scriptrunner, line 53, in run_script_stmt > Module MySQLdb.cursors, line 174, in execute > Module MySQLdb.connections, line 36, in defaulterrorhandler > OperationalError: (2006, 'MySQL server has gone away') > > This is happening across at least two separate instances with separate > storages. Not sure if this is the same, but I've gotten this error with python-mysql in a case where the mysql connection had timed out. IIRC the workaround was to adjust mysql's wait_timeout parameter. David
---------- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev