Hello,
Le dimanche 03 octobre 2021, Sébastien Helleu a écrit :
> In my case, setting "WSGIApplicationGroup" to "%{GLOBAL}" doesn't help much.
>
> But I found another solution, by enabling Daemon mode, as recommended by the
> Django docs:
> https://docs.djangoproject.com/en/3.2/howto/deployment/wsgi/modwsgi/#using-mod-wsgi-daemon-mode
>
> So I added these two lines in each site (with appropriate domain name) and it
> works fine:
>
> WSGIDaemonProcess example.com
> WSGIProcessGroup example.com
When we upgraded tracker.debian.org to bullseye, we were already using
"daemon mode" as recommended by the documentation but we still had the
above issue and setting "WSGIApplicationGroup" to "%{GLOBAL}" did
indeed fix the issue for us.
Adrian Bunk thinks that it could be fixed by
https://github.com/GrahamDumpleton/mod_wsgi/commit/9509e178e0583435a800b006b410df74e405e2b9
It would be nice if someone could double check that... we don't want to
use tracker.debian.org for that kind of test.
Cheers,
--
Raphaël Hertzog
