[Zope-ZEO] One ZSS : Multiple Data.fs files

[Bill Anderson]

Jim Fulton wrote:
[...]

> > I found through trial and error, and a little python experience, that I needed to drop the
> > '.py'.
> 
> Oops. Sorry.

ehh, it happens :)
I do most of my ZEO work at around 2-5am, so I tend to gloss over those types of things.
:)

 
> > Unfortunately ...
> >
> >   File "lib/python/ZEO/start.py", line 217, in ?
> >     if __name__=='__main__': main(sys.argv)
> >   File "lib/python/ZEO/start.py", line 173, in main
> >     storages[n]=get_storage(m,n)
> >   File "lib/python/ZEO/start.py", line 109, in get_storage
> >     im=imp.load_module(m, im[0], im[1], im[2])
> >   File "/data/SiteOne.py", line 3, in ?
> >     SiteOne=ZODB.FileStorage.FileStorage('/data/SiteOne.fs')
> >   File "/home/ZSS/Zope2/lib/python/ZODB/FileStorage.py", line 262, in __init__
> >     lock_file(f)
> >   File "/home/ZSS/Zope2/lib/python/ZODB/lock_file.py", line 101, in lock_file
> >     raise error, (ZODB.POSException.StorageSystemError: Could not lock the database file.
> > There must be another process that has opened the file.
> >
> > Despite the fact that there are no lock files, and no other python processes running.
> 
> This is not a ZEO issue. I'd double check for other processes
> and also check security settings.

So, ZEO is seeing it fine, that's good. But, lsof shows nothing using the file, there are
no lock files, permissions are fine, and a clean reboot  to ensure nothing still running
undetectable doesn't change things. I'll try on a new machine, just for sake of
compeltenss. :) if it still fails, I'll send the thread to zope-dev.
 
> Jim
> 
> --
> Jim Fulton           mailto:jim@digicool.com   Python Powered!
> Technical Director   (888) 344-4332            http://www.python.org
> Digital Creations    http://www.digicool.com   http://www.zope.org
> 
> Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
> address may not be added to any commercial mail list with out my
> permission.  Violation of my privacy with advertising or SPAM will
> result in a suit for a MINIMUM of $500 damages/incident, $1500 for
> repeats.

--
Do not meddle in the affairs of sysadmins, for they are easy to annoy,
and have the root password.