[Zope] Re: Help!!! Zope won't start -- StorageSystemError

[Dan Gaibel]

At 07:22 PM 8/27/2005 -0400, Tres Seaver wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Dan Gaibel wrote:
> > Hi folks,
> >
> > This is my first post to this list and I'm desperate for help. I'm
> > running Zope 2.6.1 with Python 2.1.3. My Zope instance died today and
> > won't come back. When I try to start it, I get:
> >
> > 2005-08-27T20:58:15 PANIC(300) z2 Startup exception
> > Traceback (innermost last):
> >   File /home/lrc/z2.py, line 497, in ?
> >   File <string>, line 1, in ?
> >   File /home/lrc/lib/python/Zope/__init__.py, line 37, in ?
> >   File /home/lrc/lib/python/ZODB/FileStorage.py, line 213, in __init__
> >   File /home/lrc/lib/python/ZODB/lock_file.py, line 33, in lock_file
> > StorageSystemError: Could not lock the database file.  There must be
> > another process that has opened the file.
> > <p>
> >
> >
> > ------
> > 2005-08-27T20:58:15 PROBLEM(100) zdaemon zdaemon: Sat Aug 27 16:58:15
> > 2005: The kid, 1657, died on me.
> >
> > At first I deleted Data.fs.lock and cannot find any process that would
> > suggest zope is running. I've also played with renaming various .pid
> > files in hopes of an answer. I'm stumped and in very hot water right
> > now. Any help or guidance would be very appreciated.
>
>Can you run 'lsof' against your Data.fs?  or run 'killall python' (not
>as root, unless Zope is the only process which might be running Python).

Thanks for the quick response! lsof gives me nothing, and I still have 
trouble when all python processes are killed. Even after a reboot. I 
thought it might be a corrupt Data.fs or something, but I can get it to 
start on another instance of zope. Could it be some lock file that I don't 
know about? I'm stumped.

Thanks,

Dan