<br><tt><font size=2>> <br>
> Wolfgang Lausenhammer wrote:<br>
> > <br>
> > LockError: Couldn't lock <br>
> > 'D:\\workspace_zope\\xla-2008/var/Stdcontainer_o.fs.lock'<br>
> <br>
> Can the user the zope process is running as write to this file?<br>
> (or create it, since it likely doesn't exist?)<br>
</font></tt>
<br><tt><font size=2>The file is existing. I tried to delete all the .index,
.lock, .tmp files in the var-folder and zope re-creates them on calling
the /manage site, so there shouldn't be a problem with writing-permissions</font></tt>
<br><tt><font size=2><br>
> > TypeError: not all arguments converted during string formatting<br>
> > Traceback (most recent call last):<br>
> > File "D:\zope\2.11.1\Python\Lib\logging\__init__.py",
line 731, in emit<br>
> > File "D:\zope\2.11.1\Python\Lib\logging\__init__.py",
line 617, in format<br>
> > File "D:\zope\2.11.1\Python\Lib\logging\__init__.py",
line 405, in format<br>
> > <br>
> > File "D:\zope\2.11.1\Python\Lib\logging\__init__.py",
line 276, in <br>
> > getMessage<br>
> > self.cfg.eventlog()<br>
> <br>
> This looks like a bug. Would be good to find where the incorrect logging
<br>
> call is and fix it :-S<br>
</font></tt>
<br><tt><font size=2>With the old 2.7.4 version it does work. I also tried
to upgrade it in steps, with zope-2.8.6 it still works and none of those
two error messages appear. With zope-2.9.8 at least one of these errors
appeared. Has there anything changed in the interface within those versions?</font></tt>
<br>
<br><font size=3>The changelog of 2.9.0 says: "Zope now utilizes ZODB
3.6. It had previously used ZODB 3.4. As a result, the DBTab package was
removed, as ZODB 3.6 has multidatabase support that makes DBTab unnecessary."</font>
<br><font size=3>Could this cause those errors?</font>
<br>
<br><font size=3>-- Wolfgang</font>