Wolfgang Lausenhammer wrote at 2008-8-4 09:56 +0200:
I just tried to lock the file manually and it works
But I recognized when zope reports those errors with locking, the reported
file can't be opened in the filesystem also, so it is really locked. It
seems that zope doesn't unlock it and so if
Thank you for your answer.
I just tried to lock the file manually and it works
But I recognized when zope reports those errors with locking, the reported
file can't be opened in the filesystem also, so it is really locked. It
seems that zope doesn't unlock it and so if zope tries to access it
Wolfgang Lausenhammer wrote at 2008-8-1 09:20 +0200:
...
__init__
File D:\zope\2.11.1\Zope\lib\python\ZODB\lock_file.py, line 42, in
_lock_file
LockError: Couldn't lock
'D:\\workspace_zope\\xla-2008/var/Stdcontainer_o.fs.lock'
A look at the code reveals:
# Windows
def
Wolfgang Lausenhammer wrote:
LockError: Couldn't lock
'D:\\workspace_zope\\xla-2008/var/Stdcontainer_o.fs.lock'
Can the user the zope process is running as write to this file?
(or create it, since it likely doesn't exist?)
TypeError: not all arguments converted during string formatting
Wolfgang Lausenhammer wrote:
LockError: Couldn't lock
'D:\\workspace_zope\\xla-2008/var/Stdcontainer_o.fs.lock'
Can the user the zope process is running as write to this file?
(or create it, since it likely doesn't exist?)
The file is existing. I tried to delete all the .index,
