> On 13 May 2024, at 2:33 PM, A McBain <mcbain....@gmail.com> wrote:
>
> The old one is running on the same physical server, just with its own Apache
> config and own subdomain. As to having multiple things running, that's why I
> set WSGIApplicationGroup to %{SERVER} but just in case I changed it
> explicitly to "enfilade.asmcbain.net <http://enfilade.asmcbain.net/>" (no
> effect, but shouldn't hurt anything to keep the change).
The WSGIApplicationGroup directive sets which Python interpreter context is
used. It is distinct from the daemon process group.
You want each WSGI application instance to run in a different mod_wsgi daemon
process group if using the main Python interpreter context (application group
%{GLOBAL}).
So what you want is for each VirtualHost to use a different named mod_wsgi
dameon process group.
<VirtualHost ...>
ServerName site-1.example.com
WSGIDaemonProcess site-1 \
user=asmcbain group=asmcbain \
display-name='%{GROUP}' \
lang='en_US.UTF-8' \
locale='en_US.UTF-8' \
threads=5 \
queue-timeout=45 \
socket-timeout=60 \
connect-timeout=15 \
request-timeout=60 \
inactivity-timeout=0 \
startup-timeout=15 \
deadlock-timeout=60 \
graceful-timeout=15 \
eviction-timeout=0 \
restart-interval=0 \
shutdown-timeout=5 \
maximum-requests=0 \
python-home=/home/asmcbain/enfilade/.env \
python-path=/home/asmcbain/enfilade
WSGIProcessGroup site-1
WSGIApplicationGroup %{GLOBAL}
WSGIScriptAlias / /home/asmcbain/enfilade/atcid/wsgi.py
</VirtualHost>
<VirtualHost ...>
ServerName site-2.example.com
WSGIDaemonProcess site-2 \
user=asmcbain group=asmcbain \
display-name='%{GROUP}' \
lang='en_US.UTF-8' \
locale='en_US.UTF-8' \
threads=5 \
queue-timeout=45 \
socket-timeout=60 \
connect-timeout=15 \
request-timeout=60 \
inactivity-timeout=0 \
startup-timeout=15 \
deadlock-timeout=60 \
graceful-timeout=15 \
eviction-timeout=0 \
restart-interval=0 \
shutdown-timeout=5 \
maximum-requests=0 \
python-home=/home/asmcbain/enfilade/.env \
python-path=/home/asmcbain/enfilade
WSGIProcessGroup site-2
WSGIApplicationGroup %{GLOBAL}
WSGIScriptAlias / /home/asmcbain/enfilade/atcid/wsgi.py
</VirtualHost>
So each site should have different name to WSGIDaemonProcess, with matching
WSGIProcessGroup, and WSGIApplicationGroup should be %{GLOBAL} for both, not
{SERVER}.
The {SERVER} value has a different meaning and best avoiding it.
So lets make sure each is running in separate daemon process groups.
BTW, also make sure that somewhere outside of all VirtualHost definitions you
add:
WSGIRestrictEmbedded On
This will cause an error if mod_wsgi daemon process groups aren't being
configured properly.
Graham
>
> This is the result of the wsgi.prod.py <http://wsgi.prod.py/> printouts:
>
> [Sun May 12 21:29:11.788518 2024] [wsgi:error] [pid 5671:tid 140047682610880]
> sys.prefix '/home/asmcbain/enfilade/.env'
> [Sun May 12 21:29:11.788639 2024] [wsgi:error] [pid 5671:tid 140047682610880]
> sys.path ['/home/asmcbain/enfilade', '/usr/lib/python311.zip',
> '/usr/lib/python3.11', '/usr/lib/python3.11/lib-dynload',
> '/home/asmcbain/enfilade/.env/lib/python3.11/site-packages']
>
> Alastair
>
> On Sun, May 12, 2024 at 9:24 PM Graham Dumpleton <graham.dumple...@gmail.com
> <mailto:graham.dumple...@gmail.com>> wrote:
>>
>> On 13 May 2024, at 2:02 PM, A McBain <mcbain....@gmail.com
>> <mailto:mcbain....@gmail.com>> wrote:
>>>
>>> Hi, I looked at previous messages and others on StackOverflow but none seem
>>> to solve my issue.
>>>
>>> I have an app I wrote working perfectly fine under Python 3.11 with
>>> mod_wsgi and Apache 2.
>>>
>>> I did a bunch of development on the app (upgraded django, new features),
>>> and set up a new checkout of that on my server, with its own virtual
>>> environment (using venv). It uses effectively the same config (different
>>> subdomain) in Apache2 as the original older copy, but the new one fails
>>> with an import error while the old one is still chugging along.
>>
>> When you say "old one is still chugging along" can you confirm you are
>> saying that the existing one is still running on the same server at the same
>> time, or it is a completely new server you have set up.
>>
>>> I double checked the instructions at
>>> https://docs.djangoproject.com/en/5.0/howto/deployment/wsgi/modwsgi/
>>>
>>> I've also re-verified the mod_wsgi I installed (via pip) matches the Python
>>> version I'm using (both are Python 3.11).
>>>
>>> I also tried:
>>> Removing the python-path argument
>>> The mod_wsgi docs suggest I don't need that if I specify python-home?
>> Removing python-path if it refers to site-packages directory of virtual
>> environment specified to python-home is okay as path would be redundant. If
>> python-path is used to tell it where your Django project is, that still
>> needs to stay.
>>> Setting WSGIApplicationGroup to %{GLOBAL}
>> That is recommended, but if you are hosting multiple WSGI applications on
>> the same server, they would need to be delegated to different mod_wsgi
>> daemon process groups.
>>
>>> Unfortunately the error didn't change at all after trying those.
>>>
>>> I've attached the relevant apache2 config section which includes all the
>>> mod_wsgi-setup (the rest is just redirects, ssl stuff, aliases, etc.)
>>>
>>> I also attached the error from the log. It looks like it's trying to use
>>> the system Python instead of the one that exists in my .env (virtual
>>> environment) directory.
>>
>> The virtual environment doesn't have a copy of Python stdlib files so they
>> are still imported from the system Python the virtual environment was
>> created from. The virtual environment effectively only has its own
>> site-packages directory.
>>
>>> I'm banging my head as to why this worked before but not now so any help is
>>> much appreciated. Thank you! 🙂
>>>
>>> Other details:
>>> wsgi.prod.py <http://wsgi.prod.py/> is the default wsgi.py, just modified
>>> to load settings.prod.py <http://settings.prod.py/>
>>> The server is Devuan Daedalus
>>
>> At the start of your WSGI script file add:
>>
>> import sys
>> print('sys.prefix', repr(sys.prefix))
>> print('sys.path', repr(sys.path))
>>
>> and check Apache logs for what paths it is using.
>>
>> Compare that to the working site.
>>
>> Post what you learn from that.
>>
>> Graham
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "modwsgi" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/modwsgi/IJp7zr6SjtY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> modwsgi+unsubscr...@googlegroups.com
>> <mailto:modwsgi+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/modwsgi/7184C263-1522-4583-A98B-EC9806B0FA66%40gmail.com
>>
>> <https://groups.google.com/d/msgid/modwsgi/7184C263-1522-4583-A98B-EC9806B0FA66%40gmail.com?utm_medium=email&utm_source=footer>.
>
>
> --
> 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 modwsgi+unsubscr...@googlegroups.com
> <mailto:modwsgi+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/modwsgi/CAGV_ScocfNc%3DSv7W7Ha3MbrM_0wq43v8U0AM3JOuNtsfP9vK%3Dw%40mail.gmail.com
>
> <https://groups.google.com/d/msgid/modwsgi/CAGV_ScocfNc%3DSv7W7Ha3MbrM_0wq43v8U0AM3JOuNtsfP9vK%3Dw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
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 modwsgi+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/modwsgi/41CA1CF3-8A06-46BF-A7AE-2CA74FCC2196%40gmail.com.
