[ZODB-Dev] POSKeyError with Zope 2.7.2, suddenly appeared, then disappeared...

[Chris Withers]

Got this error in a MailingLogger notification:

   File "/usr/local/zope/2.7.2/lib/python/ZODB/Connection.py", line 559, 
in setstate
     p, serial = self._storage.load(oid, self._version)
   File "/usr/local/zope/2.7.2/lib/python/ZEO/ClientStorage.py", line 
749, in load
     p, s, v, pv, sv = self._server.zeoLoad(oid)
   File "/usr/local/zope/2.7.2/lib/python/ZEO/ServerStub.py", line 82, 
in zeoLoad
     return self.rpc.call('zeoLoad', oid)
   File "/usr/local/zope/2.7.2/lib/python/ZEO/zrpc/connection.py", line 
372, in call
     raise inst # error raised by server
POSKeyError: 000000000014eeca

I got quite a few errors in a short-ish period of time (1 hr or so) when 
the site was getting hammered by a spider, but when I visited the URL 
the error was being reported for several hours later, it worked fine.

The corresponding error from the storage server log is:
------
2005-02-02T00:13:43 INFO(0) zrpc-conn:194.193.44.141:45508 zeoLoad() 
raised exception: 000000000014eec\
a
Traceback (most recent call last):
   File "/usr/local/zope/2.7.2/lib/python/ZEO/zrpc/connection.py", line 
264, in handle_request
     ret = meth(*args)
   File "/usr/local/zope/2.7.2/lib/python/ZEO/StorageServer.py", line 
240, in zeoLoad
     v = self.storage.modifiedInVersion(oid)
   File "/usr/local/zope/2.7.2/lib/python/ZODB/FileStorage.py", line 
735, in modifiedInVersion
     raise POSKeyError(oid)
POSKeyError: 000000000014eeca

I also see a lot of:
2005-02-02T00:13:48 INFO(0) ZSS:13738/194.193.44.141:45508 Transaction 
released storage lock

...what does that mean? and what's likely to have caused the POSKeyError 
that seems to have popped its head up, caused lots of trouble, and then 
vanished?

cheers,

Chris

-- 
Simplistix - Content Management, Zope & Python Consulting
            - http://www.simplistix.co.uk