Logging exception in LockFile handling

On Fri, Oct 2, 2009 at 2:04 AM, Andreas Jung <email address hidden> wrote:
> Public bug reported:
>
> We encountered the following traceback (ZODB 3.8) while re(starting) a
> ZEO Server in foreground:
>
> hrs2test@hdevzeo:/HRS2/ZEOServer-Zope-2.11$ bin/zeo fg
> /local/HRS2/ZEOServer-Zope-2.11/parts/zeo/bin/runzeo
> Traceback (most recent call last):
>  File "/HRS2/local/lib/python2.4/logging/__init__.py", line 731, in emit
>    msg = self.format(record)
>  File "/HRS2/local/lib/python2.4/logging/__init__.py", line 617, in format
>    return fmt.format(record)
>  File "/HRS2/local/lib/python2.4/logging/__init__.py", line 405, in format
>    record.message = record.getMessage()
>  File "/HRS2/local/lib/python2.4/logging/__init__.py", line 276, in getMessage
>    msg = msg % self.args
> TypeError: not all arguments converted during string formatting
>
> With the debugger:
> Error locking file ('/HRS2/ZEOServer-Zope-2.11/var/main/main.fs.lock', '')
>> /HRS2/local/lib/python2.4/logging/__init__.py(281)getMessage()
> -> return msg
> (Pdb) msg
> 'Error locking file'
> (Pdb) print self.args
> ('/HRS2/ZEOServer-Zope-2.11/var/main/main.fs.lock', '')
> (Pdb)
> ('/HRS2/ZEOServer-Zope-2.11/var/main/main.fs.lock', '')
>
> This is related to the call:
>
> ZODB/lock_file.py:            logger.exception("Error locking file",
> path, pid)

This is fixed on the head of the 3.8 branch. I expect it was fixed in
3.8.1 or 3.8.2.

Jim

--
Jim Fulton

This was indeed fixed in 3.8.1. 3.9.x releases don't contain thie lock_file module anymore.