HHmm, in this instance this is a VPS running ubuntu 10.something-or-other. Not particularly happy with this install for that matter.
On Sunday, November 30, 2014 4:34:13 AM UTC-5, Graham Dumpleton wrote: > > At this point I would be saying your system as a whole is rather sick. It > is highly unlikely that mod_wsgi itself could cause this. > > What you should do is use 'ps aux' to identify how many processes your > system as a whole is running and see if you can identify if anything in > particular is running a lot of processes, including possibly zombie > processes. > > After that revolt your system and try again. > > Graham > > On 30/11/2014, at 8:11 PM, Steve M <[email protected] <javascript:>> > wrote: > > I have to add another problem I just discovered. > > > It seems that when apache is running and when I try to run apt-cache > search <something> I get a segmentation fault. > When I try to run pip install <something> I get a python error dump. > > I have to stop apache in order for apt- or pip to work. > So it seems mod-wsgi is interfering with other python programs. > > So any suggestions on how to fix this and the other problem would be > greatly appreciated. > > On Sunday, November 30, 2014 1:59:07 AM UTC-5, Steve M wrote: >> >> Hello, the problem I am having is that mod_wsgi fails if I set process to >> anything greater than 1 in the WSGIDaemonProcess process=1 >> >> This is my current setup: >> [notice] Apache/2.2.14 (Ubuntu) mod_wsgi/4.4.1 Python/2.7.6 configured -- >> resuming normal operations >> >> I compiled mod_wsgi from source. >> >> This seems to be the key error, but I am guessing: >> [alert] (11)Resource temporarily unavailable: mod_wsgi (pid=1287): >> Couldn't create worker thread 9 in daemon process 'server_site_a'. >> Several of those pop up in the error log. >> >> WSGI settings in virtualhost: >> WSGIDaemonProcess server_site_a processes=1 threads=10 >> display-name=%{GROUP} >> WSGIProcessGroup server_site_a >> WSGIApplicationGroup %{GLOBAL} >> >> >> In main apache2.conf: >> WSGIRestrictedEmbedded On >> >> And mpm_worker_module settings: >> >> StartServers 10 >> MaxClients 15 >> MaxRequestsPerChild 256 >> >> MinSpareThreads 10 >> MaxSpareThreads 20 >> ThreadsPerChild 15 >> ServerLimit 80 >> >> MaxMemFree 512 >> >> >> After watching Grahams videos on making apache suck less for python I >> took some of his advice >> and decided to start fiddling with the apache settings. >> I first started off by getting apache to come up without errors using >> mpm_worker. >> Once I had a baseline for apache I started to fiddle with mod_wsgi. >> So that is how I arrived at the settings. >> >> Would appreciate any help. >> >> Thanks, >> Steve M >> > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected] <javascript:> > . > Visit this group at http://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
