Chris Withers wrote:
This is an error from the ZEO client. Can you have a look in your
storage server's log and find the corresponding error (match the
date/time). It'll hopefully hold some more clues...
It must be this one:
2005-12-09T18:46:04 INFO(0) zrpc-conn(S):127.0.0.1:33828 zeoLoad()
raised exception: 0x04b364
Traceback (most recent call last):
File "/var/www/zope/2.7.8/lib/python/ZEO/zrpc/connection.py", line
373, in handle_request
ret = meth(*args)
File "/var/www/zope/2.7.8/lib/python/ZEO/StorageServer.py", line 240,
in zeoLoad
v = self.storage.modifiedInVersion(oid)
File "/var/www/zope/2.7.8/lib/python/ZODB/FileStorage.py", line 743,
in modifiedInVersion
raise POSKeyError(oid)
POSKeyError: 0x04b364
The traceback pattern is the same in all the zeo.log poskeyerror
messages--just different oids.
/Anton
_______________________________________________
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 )
