Remove (version) locked resource
I am new to Zope; working through the Zope Book. I created a version object to test out this functioality, made changes to some objects etc. However, perhaps I didn't have 'cookies' configured properly, but some versioned changes were published on the save command and others were not. I tried to backout of what I had done using the 'Undo' feature, but it seems that I have created a right old mess now! The problem is that there is a version lock on a folder that I can't get rid of. If I start the version and then try to view the contents of the folder concerned I get this error message : Changed in a Version Site Error An error was encountered while publishing this resource. Error Type: POSKeyError Error Value: 000000000000332b Is there any way of forcing a delete version / remove lock so that I can at least try again, as opposed to uninstalling / reinstalling the whole Zope server and database? Many thanks Rod NOTICE: The information contained in this electronic mail message and any attachments is confidential to Pavilion Technologies, Inc. or one of its subsidiaries and may contain proprietary information or be legally privileged. This message and any attachments are intended only for the personal and confidential use of the designated recipient(s). If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this message in error, and that any review, dissemination, distribution or copying of this message and any attachments is unauthorised and strictly prohibited. If you have received this message in error, please notify me immediately by telephone and electronic mail, and delete this message, any attachments, and all copies thereof. Thank you very much.
At 16/12/2003 14:31, you wrote:
I created a version object to test out this functioality, made changes to some objects etc. However, perhaps I didn't have 'cookies' configured properly, but some versioned changes were published on the save command and others were not. I tried to backout of what I had done using the 'Undo' feature, but it seems that I have created a right old mess now!
Which Zope version? There was an horrible bug in FileStorage (fixed on Zope 2.6.2): when committing a version, most objects belonging to it remained locked, but the version itself was later unavailable. If this is the case, unfortunately your Data.fs is corrupt, and I dont know of any tool to repair it (should be a specific tool to repair this problema, fsrecover won't do anything). You should upgrade your Zope version and restore an old backup... Then, don't use versions and save yourself a headache... Gabriel Genellina Softlab SRL
Gabriel Genellina schrieb:
At 16/12/2003 14:31, you wrote:
I created a version object to test out this functioality, made changes to some objects etc. However, perhaps I didn't have 'cookies' configured properly, but some versioned changes were published on the save command and others were not. I tried to backout of what I had done using the 'Undo' feature, but it seems that I have created a right old mess now!
Which Zope version? There was an horrible bug in FileStorage (fixed on Zope 2.6.2): when committing a version, most objects belonging to it remained locked, but the version itself was later unavailable. If this is the case, unfortunately your Data.fs is corrupt, and I dont know of any tool to repair it (should be a specific tool to repair this problema, fsrecover won't do anything). You should upgrade your Zope version and restore an old backup... Then, don't use versions and save yourself a headache...
Its repaireable - just export all objects and reimport them again in a clean Data.fs. Regards Tino
At 16/12/2003 09:15, you wrote:
Which Zope version? There was an horrible bug in FileStorage (fixed on Zope 2.6.2): when committing a version, most objects belonging to it remained locked, but the version itself was later unavailable. If this is the case, unfortunately your Data.fs is corrupt, and I dont know of any tool to repair it (should be a specific tool to repair this problema, fsrecover won't do anything). You should upgrade your Zope version and restore an old backup... Then, don't use versions and save yourself a headache...
Its repaireable - just export all objects and reimport them again in a clean Data.fs.
Are you sure? I had a similar problem and could not fix it with export+import, but maybe it was an unrelated issue. AFAIK, export uses the current version of objects (if any) and, as you can't start working in the version, at most you would be able to export the original content, but not the changes. Gabriel Genellina Softlab SRL
Gabriel Genellina wrote at 2003-12-15 23:41 -0300:
... Then, don't use versions and save yourself a headache...
We used a Version yesterday to upgrade indexes in our production servers ("FieldIndex" --> "DateIndex", "TextIndexNG" --> "TextIndexNG2"). Without a Version, this would have meant a 1 hour downtime; with a Version, no downtime. "Version"s are useful sometimes -- of course, there should not be fatal "Version" related bugs... -- Dieter
Rod Thorburn wrote at 2003-12-16 14:31 +1300:
I created a version object to test out this functioality, made changes to some objects etc. However, perhaps I didn't have 'cookies' configured properly, but some versioned changes were published on the save command and others were not. I tried to backout of what I had done using the 'Undo' feature, but it seems that I have created a right old mess now!
The problem is that there is a version lock on a folder that I can't get rid of. If I start the version and then try to view the contents of the folder concerned I get this error message : Changed in a Version Site Error An error was encountered while publishing this resource. Error Type: POSKeyError Error Value: 000000000000332b Is there any way of forcing a delete version / remove lock so that I can at least try again, as opposed to uninstalling / reinstalling the whole Zope server and database?
You seem to use Zope 2.6.1. This version contains a serious "Version" related bug. Undo your "Version save" transaction (this should reactivate the version), upgrade to Zope 2.6.2 (which fixes the bug) and then save your Version again. -- Dieter
participants (4)
-
Dieter Maurer -
Gabriel Genellina -
Rod Thorburn -
Tino Wildenhain