Poskey Errors and BTreeFolder
Hi there, After five years with plenty of Zope/Plone sites running we are now facing our first ZODB problems: Poskey Errors popping up here and there. And it seems that they are all related to BTreeFolder based objects, e.g. * The CMF/Plone "Member" Folder * portal_memberdata (the CMFMember version) * Archetypes reference_catalog We know how to find (fsrefs.py) and remove them, however new poskey errors are showing up from time to time. Any ideas of how to hunt down what's causing this? And are BTreeFolders particular fragile? /Anton Stonor
Anton Stonor 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? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
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. Tracebacks such as: 2005-12-09T18:46:04 ERROR(200) ZODB Couldn't load state for 0x04b364 Traceback (most recent call last): File "/var/www/zope/2.7.8/lib/python/ZODB/Connection.py", line 597, in setstate p, serial = self._storage.load(oid, self._version) File "/var/www/zope/2.7.8/lib/python/ZEO/ClientStorage.py", line 757, in load p, s, v, pv, sv = self._server.zeoLoad(oid) File "/var/www/zope/2.7.8/lib/python/ZEO/ServerStub.py", line 82, in zeoLoad return self.rpc.call('zeoLoad', oid) File "/var/www/zope/2.7.8/lib/python/ZEO/zrpc/connection.py", line 489, in call raise inst # error raised by server POSKeyError: 0x04b364 /Anton
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): File "/var/www/zope/2.7.8/lib/python/ZODB/Connection.py", line 597, in setstate p, serial = self._storage.load(oid, self._version) File "/var/www/zope/2.7.8/lib/python/ZEO/ClientStorage.py", line 757, in load p, s, v, pv, sv = self._server.zeoLoad(oid) File "/var/www/zope/2.7.8/lib/python/ZEO/ServerStub.py", line 82, in zeoLoad return self.rpc.call('zeoLoad', oid) File "/var/www/zope/2.7.8/lib/python/ZEO/zrpc/connection.py", line 489, in call raise inst # error raised by server POSKeyError: 0x04b364
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... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
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
participants (2)
-
Anton Stonor -
Chris Withers