We're getting several ZMySQLDA exceptions in our logs right before one of our ZEO clients locks up. My reading of the errors below is some sort of network interruption, but I wanted to post and see if anyone else had any ideas about what might be happening. 2003-10-09T06:15:30 ERROR(200) ZMySQLDA exception during _begin Traceback (innermost last): File /var/www/zope/ZEOZOPE/lib/python/Products/ZMySQLDA/db.py, line 367, in _begin OperationalError: (2013, 'Lost connection to MySQL server during query') ------ 2003-10-09T06:15:37 INFO(0) ZServer Incoming connection from 12.47.113.36:59502 ------ 2003-10-09T06:15:38 INFO(0) ZServer Successful login. ------ 2003-10-09T06:15:53 ERROR(200) ZODB A storage error occured during transaction abort. This shouldn't happen. Traceback (innermost last): File /var/www/zope/zope262c1/lib/python/ZODB/Transaction.py, line 262, in commit File /var/www/zope/zope262c1/lib/python/ZODB/Transaction.py, line 393, in _commit_error AttributeError: Surrogate instance has no attribute '_p_oid' ------ 2003-10-09T06:15:53 INFO(0) ZODB conflict error at /VirtualHostBase/http/fredericksburg.com:80//VirtualHostRoot/gtl/churches/ (2 conflicts since startup at 2003-10-08T18:09:23) ------ 2003-10-09T06:16:00 ERROR(200) ZMySQLDA exception during _begin Traceback (innermost last): File /var/www/zope/ZEOZOPE/lib/python/Products/ZMySQLDA/db.py, line 367, in _begin OperationalError: (2013, 'Lost connection to MySQL server during query') ------ 2003-10-09T06:16:00 PANIC(300) ZODB A storage error occurred in the last phase of a two-phase commit. This shouldn't happen. Traceback (innermost last): : File /var/www/zope/zope262c1/lib/python/ZODB/Transaction.py, line 401, in _commit_error File /var/www/zope/zope262c1/lib/python/Shared/DC/ZRDB/TM.py, line 60, in abort File /var/www/zope/ZEOZOPE/lib/python/Products/ZMySQLDA/db.py, line 405, in _abort error: release unlocked lock