[ZODB-Dev] Massive LockError: Couldn't lock....check_size.lock messages

Jim Fulton jim at zope.com
Tue Apr 15 16:21:54 CEST 2014


On Tue, Apr 15, 2014 at 9:28 AM, Andreas Jung <lists at zopyx.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi there,
>
> we have a Plone 4.2 setup running ZEO with 3 application servers
> and a non-shared blob setup, ZODB3-3.10.5-py2.7-linux-i686
>
> We see massive amounts of the following error message on every
> application server. The application servers are configured
> to use a local blob-cache directory. We tried to tune the blob
> cache size (even down to zero) but without success.
>
> Any idea about this issue?

This is a missfeature in zc.lockfile.  It's crying wolf.
(Well, not really, but it has know way of knowing if the
lock is important. Sometimes it is, and sometimes not.)

These messages can be ignored.

If someone wanted to fix this, they could add an argument
to the constructor to suppress these log messages.

In the mean time, as a work around, you could adjust your logger
configuration to suppress these yourself.

Jim

>
> Andreas
>
> 2014-04-15T15:24:34 ERROR zc.lockfile Error locking file
> /srv/gehirn/dasgehirn_buildout/var/blobstorage.cache/check_size.lock;
> pid=25381
> Traceback (most recent call last):
>   File
> "/srv/gehirn/dasgehirn_buildout/eggs/zc.lockfile-1.0.2-py2.7.egg/zc/lockfile/__init__.py",
> line 84, in __init__
>     _lock_file(fp)
>   File
> "/srv/gehirn/dasgehirn_buildout/eggs/zc.lockfile-1.0.2-py2.7.egg/zc/lockfile/__init__.py",
> line 59, in _lock_file
>     raise LockError("Couldn't lock %r" % file.name)
> LockError: Couldn't lock
> '/srv/gehirn/dasgehirn_buildout/var/blobstorage.cache/check_size.lock'
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQGUBAEBAgAGBQJTTTPkAAoJEADcfz7u4AZjY7oLvjOM2VyMng1g8QDnQheQ8MCY
> pEjxNGTfKskZKJaeYdbOBsSAGC46dYEQNee56CRbPO+G4QsjXDnMjPGIrbUF9/CD
> DeEA5wiCeTkb/Y7WRhfqvCDuLmIHEY0oYeFlpXH2bQ62uTGA4BD1EnvYi6wJKurH
> WsM4JU5X+KzHJhC867M5fFpL0r0kLXVHNovY9q3zCdrS4kqTPr/OEgKKPpI4ytIK
> BDpRtV7ZRPKE0Kgi6mJAPYr6F541BqMVQdCrK14LtbKCwcJDbrrVcsM+eZSjI9AN
> wqtVB30OwfRQiYFBRmRfm8ncHrALx4W4a6rvvoMAp9uf7F8cuIRRIvW4vymIxiR0
> a2jfal2PR0QwM4XW7tb/42lhE1Gvwmd0VPk+bSg6MHYoMB78j6wOnBjlot3BJADS
> kXpTnYXAkHLe+PQX7JROX53C67f/pN1rXkr9VwEGWKWQaODS26n2IachD5fs8AC5
> a38Jo3EcR3cTIYiZady62M7muJqkJO4=
> =UF30
> -----END PGP SIGNATURE-----
> _______________________________________________
> For more information about ZODB, see http://zodb.org/
>
> ZODB-Dev mailing list  -  ZODB-Dev at zope.org
> https://mail.zope.org/mailman/listinfo/zodb-dev



-- 
Jim Fulton
http://www.linkedin.com/in/jimfulton


More information about the ZODB-Dev mailing list