On 12/22/21 8:50 PM, Mark Sapiro wrote:
On 12/22/21 7:54 PM, David Newman wrote:
On 12/22/21 7:29 PM, Mark Sapiro wrote:
This looks like a uwsgi issue as discussed at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U... although that's with apache and not nginx so it may not be.
If I'm reading the thread correctly, it's Apache workarounds to an underlying Debian issue, so I agree it may not apply with nginx.
I think you're correct that it doesn't apply to nginx, but the symptom is not the same. It is not a Debian issue per se. It is an Apache change that got installed with a Debian update, but the underlying issue is with Apache. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
There are 260 files named 'urls.py' under /opt/mailman, mostly for socialaccount stuff.
Where does that change go? All files? Or just this one:
/opt/mailman/venv/lib/python3.9/site-packages/postorius/urls.py
Not that one. The one whose content looks like https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py. It is probably in the same directory as your Django settings.
On my system that file lives here:
/opt/mailman/venv/lib/python3.9/site-packages/mailman_web/urls.py
But the error persists after this addition and restarting MM3 and mailmanweb and nginx:
url(r'^mailman/', include('postorius.urls')),
There is this 404 error in uwsgi.log:
[pid: 73356|app: 0|req: 3/3] 127.0.0.1 () {48 vars in 1544 bytes} [Wed Dec 22 21:13:48 2021] GET /mailman/admindb/listname => generated 5328 bytes in 14 msecs (HTTP/1.0 404) 6 headers in 197 bytes (1 switches on core 0)
If this is a uwsgi issue, is there something else to tweak with that?
Thanks
dn