On Thursday 07 November 2002 1:33 pm, Bo M. Maryniuck wrote:
2002-11-07T13:34:15 INFO(0) ZODB conflict error at /projects/merch/ (18 conflicts since startup at 2002-11-07T13:30:01)
ConflictErrors are harmless in small quantities. It indicates that two concurrent transactions accessed the same objects, and it was modified by at least one.
2002-11-07T13:31:15 ERROR(200) ZODB Couldn't load state for '\x00\x00\x00\x00\x00\x00\x1c.' Traceback (innermost last): File /opt/zope/lib/python/ZODB/Connection.py, line 447, in setstate AttributeError: 'None' object has no attribute 'load'
You are not using the latest version - Zope 2.6 and ZODB 3.1 give a much nicer exception in this case. Essentially Zope is accessing an object outside of a transaction. Most likely while rendering an error message. This is a bug, but not one that anyone has given any attention.