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
_______________________________________________
Zope maillist - [email protected]
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 )
