[ZODB-Dev] Yet More POSKeyErrors

[Chris Withers]

Jeremy Hylton wrote:
> 
> Is there a traceback on the server?

It was hard to find amidst the spew of log messages whinging about the storage 
already being packed (*sigh*), but here's the matching traceback on the server:

------
2002-12-11T19:28:30 ERROR(200) ZEO Server error
Traceback (innermost last):
   Module ZEO.StorageServer, line 238, in message_input
   Module ZEO.StorageServer, line 299, in zeoLoad
   Module ZODB.FileStorage, line 663, in modifiedInVersion
POSKeyError: 0000000000073990

Does this help at all?

> Did you run fsrefs.py (from ZODB3/Tools)?  This will tell us whether
> the object actually exists.

I've just run fsrefs.py on all three of the FileStorages being served up by the 
storage server. Only one of them generated any output:

oid 0x4c24f failed to load
Traceback (most recent call last):
   File "fsrefs.py", line 67, in main
     data, serial = fs.load(oid, "")
   File "/usr/local/zope/2.6.0_cvs_19.09.02/lib/python/ZODB/FileStorage.py", 
line 619, in load
     return self._load(oid, version, self._index, self._file)
   File "/usr/local/zope/2.6.0_cvs_19.09.02/lib/python/ZODB/FileStorage.py", 
line 614, in _load
     return _loadBack(file, oid, pnv)[0], serial
   File "/usr/local/zope/2.6.0_cvs_19.09.02/lib/python/ZODB/FileStorage.py", 
line 2116, in _loadBack
     raise POSKeyError(oid)
POSKeyError: 000000000004c24f

...which doesn't tally with any of the errors showing up in the client logs, 
although obviously I'd like to know what it is and sort it out. Any ideas?

> I just wanted to note that these bugs have nothing to do with BTrees
> (as I suspected all along).  As I mentioned earlier in the week, the
> BTree-based index was accidentally disabled for Zope 2.6.

*more sigh*

Any ideas what is causing them?

cheers,

Chris