Graham Dumpleton wrote: > 2009/1/5 Alberto Valverde <[email protected]>: > >> <Location /> >> WSGIProcessGroup prod.toscawidgets.org >> </Location> >> <Location /widget/> >> WSGIProcessGroup widgetbrowser.toscawidgets.org >> </Location> >> >> WSGIScriptAlias /widget /home/www/toscawidgets/wsgi/widgetbrowser.wsgi >> WSGIScriptAlias / /home/www/toscawidgets/wsgi/twWebSite.wsgi >> >> ... >> >> Trac isn't being forced, AFAIK, to be run in the first interpreter. I've >> just added: >> WSGIApplicationGroup %{GLOBAL} >> under the "/" Location section (where trac runs at) to see if it makes a >> difference, I'll report back later today. >> > > Forcing the app to run in the global interpreter hasn't solved the segfaults. I'll try to follow the steps mentioned in [1] to debug an app running in daemon mode with gdb and send you a stack trace somewhen this week. By the way, is there any way to tell the daemon process to dump core so I can avoid babysitting apache while waiting for a crash to happen? (they're often quite sporadic). > Doing it at '/' Location will mean it will be inherited by /widget as > well. Since the widget application is in separate daemon process that > is fine. Will actually trim usage of widget daemon process by a very > small amount as will not create an additional sub interpreter. > > Normally one would use Directory to qualify process/application group, > but you have both scripts in same directory so a bit more fiddly to do > it that ways as would need to used Files directive within Directory > directive to qualify what applies to what. > Any > Anyway, %{GLOBAL} should definitely help as svn Python wrappers known > to need it. > The app should not be importing the svn bindings, AFAIK, since it is using mercurial.
Alberto [1] http://code.google.com/p/modwsgi/wiki/DebuggingTechniques --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
