>
> WSGIDaemonProcess Yanged processes=8 threads=1 display-name=%{GROUP}
>>>>> user=garito group=staff
>>>>> WSGIProcessGroup Yanged
>>>>>
>>>>
>>>> The WSGIProcessGroup is not needed as you have process-group option on
>>>> WSGIScriptAlias.
>>>>
>>>
>>> Which one do you prefer? Or What are the differences?
>>>
>>
>> Either can be used. WSGIProcessGroup will not override process-group
>> option on WSGIScriptAlias though.
>>
>> Also, if you specify both process-group and application-group options to
>> WSGIScriptAlias, it will preload the WSGI script on process start as well.
>>
>
> You mean that?: process-group=Yanged application-group=%{GLOBAL}
> I try to watch/read everything you post about mod_rewrite. I'm pretty sure
> I've put that sometime ago because I read/watch your recommendation. Glad
> to read that
>
The documentation on this isn't good. Is only noted in:
http://code.google.com/p/modwsgi/wiki/ChangesInVersion0300
See (2) under 'Features Added'.
> </VirtualHost>
>>>>>
>>>>>
>>>>> <VirtualHost *:443>
>>>>> ServerName example.net
>>>>> ServerAlias www.example.net
>>>>> ServerAdmin "[email protected]"
>>>>>
>>>>> WSGIProcessGroup Yanged
>>>>>
>>>>
>>>> Don't need WSGIProcessGroup here.
>>>>
>>>> You are also though missing:
>>>>
>>>> WSGIScriptAlias / /Users/garito/Yanged/Runner/yR****un.py
>>>> process-group=Yanged application-group=%{GLOBAL}
>>>>
>>>> <Directory "/Users/garito/Yanged/Runner">
>>>> Order deny,allow
>>>> allow from all
>>>> </Directory>
>>>>
>>>> In other words, the only bit for the mod_wsgi configuration not
>>>> duplicated is the WSGIDaemonProcess.
>>>>
>>>
>>> The only way I have to make it run is by putting the WSGIDaemonProcess
>>> outside the VS's definitions. Did I miss something or this is normal?
>>>
>>
>> If the issue is still about not finding the daemon process group name, it
>> is going to be an ordering issue. The WSGIDaemonProcess directive when
>> reaching across VIrtualHost's must be in the first VirtualHost read by
>> Apache. So, if these are in separate files and included via a wildcard,
>> likely the WSGIDaemonProcess is in the wrong one. Is also important that
>> ServerName match for both. This all presumes you are using a recent
>> mod_wsgi, although if using process-group option to WSGIScriptAlias you
>> must be using mod_wsgi 3.0+, which should be okay.
>>
>
> The error is: WSGI process group not accessible.
>
Unless something screwy is happening, that message would only come up if
the WSGIDaemonProcess is matched to was specified in a different
VirtualHost but ServerName was not the same for the two VirtualHosts.
Since you have masked what the original values are I cant confirm anything
from the details you have sent in email
Graham
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
