Whoops, somehow managed to take this off list. 2010/1/15 Graham Dumpleton <[email protected]>: > 2010/1/15 Graham Dumpleton <[email protected]>: >> 2010/1/15 Giel van Schijndel <[email protected]>: >>> On Fri, Jan 15, 2010 at 11:57:43AM +1100, Graham Dumpleton wrote: >>>> 2010/1/15 Giel van Schijndel <[email protected]>: >>>>> On 14 jan, 00:27, mog <[email protected]> wrote: >>>>>> On 13/01/2010 21:47, Graham Dumpleton wrote: >>>>>>> By removing WSGIProcessGroup you are no longer running your >>>>>>> application in daemon mode, but instead are using embedded mode. >>>>>>> Since this particular issue that is affecting you only affects >>>>>>> daemon mode, switching to embedded mode will as a result make it go >>>>>>> away. >>>>>> >>>>>> Oh bugger. Yeah, so the reason it started working in the first >>>>>> place, was because removing 'WSGIProcessGroup' was telling it to >>>>>> revert back to embedded mode. That's really frustrating, heh :| >>>>> >>>>> I seem to have the exact same problem on a FreeBSD system as well. It >>>>> runs well in embedded mode but just times out in daemon mode. >>>>> >>>>> Except for the timestamps my logs are almost exactly the same to >>>>> mog's, thus I won't quote them here right away (unless you'd want me >>>>> to). >>>>> >>>>>>> So, at least so you can move forward try with embedded mode, but I may >>>>>>> keep quizzing you about things so can work out why daemon mode isn't >>>>>>> working on FreeBSD. >>>>>> >>>>>> Yeah I'll do that, I need to crack on with the new project and make >>>>>> some progress with migrating the old ones. That's no problem, if I >>>>>> can help or provide more info that will assist with solving the >>>>>> issue, I'll certainly do what I can. I'd still like to be able to >>>>>> use daemon mode one day :) >>>>> >>>>> Thus I'm subscribing as another tester should you need one. >>>> >>>> If you are both using mod_wsgi 3.1, can you instead try mod_wsgi 2.8. >>>> >>>> There were changes to how threads were managed on daemon process side >>>> in mod_wsgi 3.1 and want to eliminate that as a cause. >>> >>> Using this before: >>>> [g...@hyde:www/mod_wsgi3]$ pkg_info | grep wsgi >>>> mod_wsgi-3.1 Python WSGI adapter module for Apache >>> >>> now: >>>> [g...@hyde:www/mod_wsgi3]$ pkg_info | grep wsgi >>>> mod_wsgi-2.8 Python WSGI adapter module for Apache >>> >>> Seems, you're right, there's a regression from 2.8 to 3.1. Downgrading >>> back to 2.8 seems to work with a daemon process (except for the >>> WSGIVerboseDebugging directive). >>> >>> Thus perhaps some deadlock or something similar has been introduced that >>> somehow only gets triggered on FreeBSD? Either way, I didn't look at the >>> code so I'm not going to be guessing much further than that. >>> >>> You're suggestion seems to work, I'll thus be running 2.8 for now. If >>> you have a patch and would like me to test it just mail me. >> >> Can you give me the result of running: >> >> ldd mod_wsgi.so >> >> for .so file from both mod_wsgi 2.8 and mod_wsgi 3.1. >> >> I am presuming here you are installing binary packages and not >> something compiled from source code. Correct? >> >> One other possibility besides mod_wsgi 3.1 code changes, is whether >> linked with same threading libraries. I understand that on some BSD >> systems there are multiple threading libraries. > > Another request. When Apache is installed, it creates a 'build' > install directory where apxs files are. In that directory is a file > called 'config.nice', eg., > > /usr/share/httpd/build/config.nice > > I would like to see the contents of that. For example, For Apple > supplied httpd is: > > "/SourceCache/apache/apache-747/httpd/configure" \ > "--prefix=/usr" \ > "--enable-layout=Darwin" \ > "--with-apr=/usr" \ > "--with-apr-util=/usr" \ > "--with-pcre=/usr/local/bin/pcre-config" \ > "--enable-mods-shared=all" \ > "--enable-ssl" \ > "--enable-cache" \ > "--enable-mem-cache" \ > "--enable-proxy-balancer" \ > "--enable-proxy" \ > "--enable-proxy-http" \ > "--enable-disk-cache" \ > "$@" > > If you don't know where the 'build' directory is located, cat the > 'apxs' script and look for: > > my $installbuilddir = "/usr/share/httpd/build";
-- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
