hmm, there's definitely no other zope process around at that time.
could it be that the index is just being recreated at that time?
(there's around 120000 objects in the db according zope's cache tab)

i'm not a zodb specialist :)
but i'd like to find out...

regards, juergen herrmann

On Wed, January 25, 2006 21:15, Dieter Maurer wrote:
> Jürgen Herrmann wrote at 2006-1-25 11:00 +0100:
>>hi!
>>
>>after upgrading to zope 2.9 i receeive the following errors for about
>>20-30s after restart:
>>
>>2006-01-25 10:54:16 ERROR ZODB.lock_file Error locking file
>>/home/bliss/zope/var/bliss_data.fs.lock
>>Traceback (most recent call last):
>>  File "/home/bliss/zope/lib/python/ZODB/lock_file.py", line 63, in
>> __init__
>>    lock_file(self._fp)
>>  File "/home/bliss/zope/lib/python/ZODB/lock_file.py", line 42, in
>> lock_file
>>    fcntl.flock(file.fileno(), _flags)
>>IOError: [Errno 11] Resource temporarily unavailable
>
> This means that the storage is opened by another process.
>
> Stop this other process and your problem should go away (unless
> your process tries to open it twice).
>
> --
> Dieter
>


_______________________________________________________________________

>> XLhost.de - eXperts in Linux hosting <<

Jürgen Herrmann
Bruderwöhrdstraße 15b, DE-93051 Regensburg

Fon:  +49 (0)700 XLHOSTDE [0700 95467833]
Fax:  +49 (0)721 151 463027
WEB:  http://www.XLhost.de

_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev

Reply via email to