Anton Stonor wrote:
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 o
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()
Anton Stonor wrote:
Right, I just thought that made little sence when it came to Poskey Errors.
There are reasons why we ask for these things...
Zope 2.7.8, Plone 2.0.5. Tracebacks such as:
2005-12-09T18:46:04 ERROR(200) ZODB Couldn't load state for 0x04b364
Traceback (most recent call last)
Chris Withers wrote:
Any ideas of how to hunt down what's causing this? And are
BTreeFolders particular fragile?
How about some tracebacks/zope version/plohn version/more information?
Right, I just thought that made little sence when it came to Poskey Errors.
Zope 2.7.8, Plone 2.0.5. Trace
