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.
I have a FreeBSD 7.2 image installed under VmWare and think I have ports installed. How do I install mod_wsgi 2.8/3.1 ports given that they aren't in standard ports tree, plus, even the ones at freshports are setup for Apache 1.3 and not Apache 2.2. http://www.freshports.org/www/mod_wsgi/ http://www.freshports.org/www/mod_wsgi3/ I have never installed FreeBSD before or used ports, so good instructions for getting Apache 2.2 and newest mod_wsgi versions installed from ports appreciated. Graham
-- 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.
