Hi there, I'm facing an issue with a ConflictError that won't go away even after restarting. Looks like the ZODB got screwed somehow. Here's the traceback:
* Module Zope.App.startup, line 163, in zpublisher_exception_hook * Module ZPublisher.Publish, line 107, in publish * Module Zope.App.startup, line 222, in commit * Module ZODB.Transaction, line 252, in commit * Module ZODB.Connection, line 738, in tpc_vote * Module ZEO.ClientStorage, line 849, in tpc_vote * Module ZEO.ClientStorage, line 833, in _check_serials ConflictError: database conflict error (oid 0xd40acd, serial this txn started with 0x0363a06b42bc2499 2006-02-24 15:39:15.641000, serial currently committed 0x0363b6ce866bdc88 2006-02-28 15:10:31.505000) The system where this is happening is running a ZEO Server and a single ZEO Client. At some point, near the date mentioned in the traceback, the system ran out of disk space during a large transaction. Could this have affected the database? What are the steps to recover from it? Maybe truncate the database? What can be done to avoid it in the future? -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev