[ZODB-Dev] KeyError / POSKeyError

2007-03-23 Thread Tim Tisdall
I've got a 1gb ZODB that contains a single plone site and I'm not able to access any part of it via the ZMI. It keeps saying that it's looking for key fammed-old which is another plone site in another ZODB file. Basically I managed to partly migrate a Plone 2.0 to Plone 2.5 and then copied

Re: [ZODB-Dev] KeyError / POSKeyError

2007-03-23 Thread Christian Theune
Hi, Can you tell whether you get a KeyError or a POSKeyError? If you get a KeyError, it's likely that the app (Plone) is broken, e.g. during the migration you mentioned. A POSKeyError would (very likely) not talk about a a key like 'fammed-old', so I suspect you don't have a corruption in your

[ZODB-Dev] Re: KeyError / POSKeyError

2007-03-23 Thread Laurence Rowe
You need to provide the full traceback so we can tell where it is coming from. My guess (though I'm surprised by the particular error) is that you have perhaps got content owned by users in a user folder outside the site that is no longer accessible when you mount the database on its own. If

Re: [ZODB-Dev] Re: KeyError / POSKeyError

2007-03-23 Thread Tim Tisdall
When I run the fsrefs.py on the database I get the following: - oid 0x0L persistent.mapping.PersistentMapping last updated: 2007-01-02 18:59:32.016077, tid=0x36AA393889A1800L refers to invalid object: oid ('\x00\x00\x00\x00\x00\x00\x00\x01', None) missing: 'unknown' oid 0x1L

Re: [ZODB-Dev] Re: KeyError / POSKeyError

2007-03-23 Thread Dieter Maurer
Tim Tisdall wrote at 2007-3-23 16:03 -0400: When I run the fsrefs.py on the database I get the following: - oid 0x0L persistent.mapping.PersistentMapping last updated: 2007-01-02 18:59:32.016077, tid=0x36AA393889A1800L refers to invalid object: oid ('\x00\x00\x00\x00\x00\x00\x00\x01',

Re: [ZODB-Dev] Re: KeyError / POSKeyError

2007-03-23 Thread Tim Tisdall
Okay, I didn't think it'd work, but I tried using a backup. It didn't work. I only have backups of the ZODB with the plone instance I want to keep. Unfortunately, it and all the backups seem to be hung up on finding the broken plone instance in a completely different ZODB. I didn't bother