[mod_python] Error:Failed to reinit global mutex

well, yes, i have upped my maxfiles / maxfiles per proc etc and it
still doesn't run.

again, the really weird thing is that mod_python / apache starts at
first, but after i make it crash, it won't start again!  i don't
understand what is changing between runs of apache, since i'm cleaning
out all temp files, looking for open files / sysv ipc stuff.....

any unix hackers out there have any ideas?  this will be my last post
since it's off-topic, sorry.

take care, B

On Thu, 11 Mar 2004, Gregory (Grisha) Trubetskoy wrote:

>
> I think this is because on startup Python can open a boatload of files
> while importing modules. I'd just up kern.maxfiles and
> kern.maxfilesperproc, especially if your apache is configured to start a
> lot of children upfront.
>
> Just FYI, my settings are:
>
> kern.maxfiles: 32808
> kern.maxfilesperproc: 29527
>
> and I don't think there is much harm in taking it much higher for a heavy
> load production system.
>
> Grisha
>
> On Thu, 11 Mar 2004, Ben wrote:
>
> > this might be more of an OS or Apache question but....
> >
> > i'm debugging something right now which seems to crash apache /
> > mod_python.  probably something i'm doing, i'm sure.  anyhow, it
> > wouldn't be much of a problem except that when it crashes, i can't
> > restart the server without rebooting.  i get errors like:
> >
> > [Thu Mar 11 10:08:51 2004] [notice] mod_python: Creating 32 session mutexes based on 50 max processes and 0 max threads.
> > (24)Too many open files: mod_python: Failed to reinit global mutex /tmp/mpmtx84815.
> > 'import site' failed; use -v for traceback
> > [Thu Mar 11 10:08:52 2004] [error] make_obcallback: could not import mod_python.apache.
> >
> > ImportError: No module named mod_python.apache
> > [Thu Mar 11 10:10:38 2004] [error] (24)Too many open files: apr_accept: (client socket)
> >
> > i've cleaned up /tmp/mpm*, /var/run/httpd.scoreboard, etc.  i've also
> > verified that in fact
> >
> > kern.openfiles: 68
> > kern.maxfiles: 12328
> >
> > and raised the openfiles limit on the www process, and checked lsof
> > which says there isn't much open.  so it looks like some kind of
> > shared memory / locking thing, except that ipcs tells me not much: i
> > guess it's not a sysv ipc thing.
> >
> > does anyone know how to clean house for this kind of stuff?
> >
> > B
> >
> > _______________________________________________
> > Mod_python mailing list
> > Mod_python at modpython.org
> > http://mailman.modpython.org/mailman/listinfo/mod_python
> >
>