[mod_python] ValueError: Failed to acquire global mutex lock

If you run 'ipcs' what is the output? Something must be using all the
semaphores, can't be anything else.

Graham

On 24/10/2007, Michael Robokoff <mike.robokoff at apioutsourcing.com> wrote:
> Ok the directive did take effect as the log entry below shows:
>
> [Tue Oct 23 07:20:32 2007] [notice] mod_python: Creating 4 session mutexes
> based on 6 max processes and 25 max threads.
> [Tue Oct 23 07:20:32 2007] [notice] mod_python: using mutex_directory /tmp
>
>
> Still see this however:
>
> ValueError: Failed to acquire global mutex lock
>
> I will try recompiling with the option you mentioned and see what happens.
>
>
> --Mike
>
>
> -----Original Message-----
> From: Graham Dumpleton [mailto:graham.dumpleton at gmail.com]
> Sent: Tuesday, October 23, 2007 6:40 AM
> To: Michael Robokoff
> Cc: mod_python
> Subject: Re: [mod_python] ValueError: Failed to acquire global mutex lock
>
> On 23/10/2007, Michael Robokoff <mike.robokoff at apioutsourcing.com> wrote:
> > [Thu Oct 18 07:37:38 2007] [notice] mod_python: Creating 8 session mutexes
> > based on 6 max processes and 25 max threads.
>
> BTW, what did you end up setting mod_python.mutex_locks to? If you use
> 4 like I said, then it can't have been in correct part of Apache
> configuration, outside of all VirtualHost, as error log still shows '8
> session mutexes'.
>
> if you can't get this to work, you might rebuild mod_python and
> specific --with-max-locks=4 option to configure to force lower value
> to be compiled in.
>
> Graham
>
>
>