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

[Andreas Jung]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jim Fulton wrote:
> On Tue, Apr 15, 2014 at 9:28 AM, Andreas Jung <lists at zopyx.com>
> wrote: 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.

Could you please check this PR?

https://github.com/zopefoundation/zc.lockfile/pull/3

Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQGUBAEBAgAGBQJTTXx7AAoJEADcfz7u4AZjvfsLv08c1qhS2OBq80z/xrJ7zjyS
rJX9BhPKEWqT2R4lIirVwLj00OctMW/WrxpiI0e4hsCzTpK+aqRnvu6lzUru3Rw+
SVgKfX/XcPg4CCNFVBErVkdzbpYeeShrmOrfgXJwOwBpl4sQyYdpH71KQWH8Lyj6
1szQjJPk0JfrjiLxPrbnAJfYO7SBcNEMvGSwOTW5ilKm0mVMyI6XlwoJSetrY/PE
w9CLN5JHh1Q0tIxcHOE3nEgYoHVlS4M2Kd4gWC+JDtjZ6ntqZu5h6NgROGkrGMZT
eIUL5c41R6ld1Cwr/g5ljA+8UVKIwtEFfdhzny2BbDu2quhEqf/5kRNe6s5fqI45
bQ8BLeLHs1SslzeMXJqsNNjIIBpmtqcyjr4KJGesgMlB6yp2+6W3QXpTpGmCHmzj
ICPCWIvextWYp2fMkRI9uxpc3JTcBnDOHW3j0/ujW+yi+uL+SLS3+9/yNZsdhPH8
8loEePwI/4mLjOlxRULOzbceIRep73c=
=N25/
-----END PGP SIGNATURE-----