[ZODB-Dev] weird "MySQL gone away error" when viewing history tab on Script(Python) with RelStorage 1.4.2
Shane Hathaway
shane at hathawaymix.org
Wed Apr 27 13:11:48 EDT 2011
On 04/27/2011 05: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.
>
> Any ideas?
Maybe the query is killing MySQL, for whatever reason. Are the MySQL
process IDs the same before and after this happens?
Shane
More information about the ZODB-Dev
mailing list