This is actually nothing to worry about. The error message doesn't take into account that the error it's reporting could be a conflict error (these are normal errors seen during Zope execution). The catalog probably shouldn't bother logging the error in this case. On Sep 9, 2005, at 4:16 AM, Marco Bizzarri wrote:
We are seeing traceback in the event log like this:
2005-09-09T09:28:32 ERROR(200) KeywordIndex unindex_object could not remove documentId -702398584 from index w orkitems_from. This should not happen. Traceback (most recent call last): File "/home/zope/zope-2.7.4/lib/python/Products/PluginIndexes/ common/UnIndex.py", line 185, in removeForward IndexEntry indexRow.remove(documentId) File "/home/zope/zope-2.7.4/lib/python/ZODB/Connection.py", line 599, in setstate invalid = self._is_invalidated(obj) File "/home/zope/zope-2.7.4/lib/python/ZODB/Connection.py", line 628, in _is_invalidated raise ReadConflictError(object=obj) ReadConflictError: database read conflict error (oid 0x38f00c, class BTrees.IIBTree.IISet)
What is the meaning of the first line? Is it something we should worry about? (workitems_from is an index of the ZCatalog, of course). -- Icube Srl http://www.icube.it/ _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )