Many thanks Dieter for your pointers... ----- Original Message ----- From: "Dieter Maurer" <dieter@handshake.de> To: "Gilles Lenfant" <gilles@pilotsystems.net> Cc: <zope@zope.org> Sent: Tuesday, October 21, 2003 10:57 PM Subject: Re: [Zope] VersionLockError ???
Gilles Lenfant wrote at 2003-10-21 16:26 +0200:
I sometimes got this in random (?) places in a Zope 2.6.1 box
Error Type: VersionLockError Error Value: ("'\\x00\\x00\\x00\\x00\\x00\\x00\\x04\\xfe'", '/stuff/versionMenus')
Zope 2.6.1 had a nasty bug with its Version support.
I noticed this :)
If you are lucky, then you can abort the versions via "Control_Panel --> Version Management".
Says "There are no non-empty versions." Seems I'm not lucky.
If you are unlucky, your ZODB is corrupted and it might be difficult to get rid of these errors again.
Seems that it's the case... I made a new Zope 2.6.2 instance, with the same products, then copied the Data.fs to that new instance. That new instance refuses to start : raising the same exception, then stopping (panic mode). Do you think that starting a new Zope 2.6.2 instance with the same products and a virgin Data.fs then exporting/importing all folders at root as zexps would fix this ? $ python utilities/ZODBTools/fstest.py -v var/Data.fs ... var/Data.fs truncated possibly because of damaged records at 1117825536 But I dunno how to fix this... Cheers --Gilles