[ZODB-Dev] Exception when closing database
Arve Knudsen
arve.knudsen at gmail.com
Wed Feb 14 10:34:42 EST 2007
Hi
I sometimes receive an exception when closing a ZODB, due to it trying to
remove a lock file which doesn't exist. Given the backtrace can you tell me
whether this is something which should be rectified in ZODB? I suspect the
problem lies in the fact that the database is closed from atexit, maybe ZODB
has already registered some kind of cleanup from atexit?
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "/home/arve/Projects/Conduit/cdt_testing/common.py", line 63, in
close
self.instlCtlg.close()
File "/home/arve/Projects/Conduit/conduit/installed.py", line 477, in
close
self._db.close()
File "/home/arve/Projects/Conduit/conduit/_database.py", line 24, in close
try: self._db.close()
File "/usr/lib/python2.4/site-packages/ZODB/DB.py", line 431, in close
self._storage.close()
File "/usr/lib/python2.4/site-packages/ZODB/FileStorage/FileStorage.py",
line 400, in close
self._lock_file.close()
File "/usr/lib/python2.4/site-packages/ZODB/lock_file.py", line 74, in
close
os.unlink(self._path)
OSError: [Errno 2] No such file or directory:
'/tmp/tmpCuD9cO/.conduit/storage/storage.fs.lock'
Thanks,
Arve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.zope.org/pipermail/zodb-dev/attachments/20070214/0aab52fc/attachment.htm
More information about the ZODB-Dev
mailing list