[mod_python] ValueError: Failed to acquire global mutex lock

Julian Ciccale jciccale at mac.com
Sun Nov 23 13:24:26 EST 2003

Hi and thanks,
  I got that problem solved but now it seems it's happening something weird. I compiled the sources from CVS (enabling the debugging lines on the locking calls). On a first request i get these lines:

[Sun Nov 23 12:17:51 2003] [warn] _global_lock at index 30 from pid 21429
[Sun Nov 23 12:17:51 2003] [warn] _global_lock DONE at index 30 from pid 21429

, which seems to lock mutex at ix 30. (and remains locked even when the request has completed). Then when a second request comes i get this:

[Sun Nov 23 12:18:02 2003] [warn] _global_lock at index 30 from pid 21425

. Obviously that process remains locked forever, waiting on a lock forever.
How it was meant to work the locking mechanism? It seems the problem is in Session.py and how it handles the locking..

BTW. I'm working on a very cool project take a look (pythonwork.sf.net)

On Sunday, November 23, 2003, at 03:43AM, Gregory (Grisha) Trubetskoy <grisha at modpython.org> wrote:

>See if you can get the latest sources from CVS - I believe this has been
>fixed soon after 3.1.1b was released.
>On Sun, 23 Nov 2003, Julian Ciccale wrote:
>> Hi,
>>    I'm running RH 9 with apache 2.0 (prefork) and modpython 3.1.1b.
>> Sadly I'm unable to use the new Session handling classes, I get "Failled
>> to acquire global mutex lock" and this on apache's error log
>>   "(13)Permission denied: Failed to acquire global mutex lock at index 9"
>>  Anyone that is getting the same errors?
>> Thanks,
>> Julian
>> _______________________________________________
>> Mod_python mailing list
>> Mod_python at modpython.org
>> http://mailman.modpython.org/mailman/listinfo/mod_python

More information about the Mod_python mailing list