On 2/11/22 13:32, gordon@dickens.com wrote:
Hi Mark,
I think that I found a hint as to the cause of my problems.
I changed the apache2 LogLevel to debug and the following was then generated in /var/log/apache2/ssl_error_log:
[Fri Feb 11 15:40:18.325675 2022] [core:debug] [pid 3982011] core.c(5280): (95)Operation not supported: [remote /var/lib/mailman3/web/static/uwsgi.sock:12150] AH00139: apr_socket_opt_set(APR_TCP_NODELAY)
Apparently, there appears to be a problem with uwsgi.sock.
My uwsgi.ini file has the following:
uwsgi-socket = /var/lib/mailman3/web/static/uwsgi.sock
Also, my apache.conf for mailman3 has the followig:
ProxyPass /mailman3 unix:/var/lib/mailman3/web/static/uwsgi.sock|uwsgi://localhost
So do you see a problem in my configuration files that would cause the Operation Not Supported error with the uwsgi.sock file.
I don't use uWSGI and have no experience with it at all, however here are some things to consider:
For Apache to support uwsgi protocol you may need
a2enmod mod_proxy_uwsgi
However, I would suggest you use http rather than a unix socket.
In your uwsgi.ini file instead of
uwsgi-socket = /var/lib/mailman3/web/static/uwsgi.sock
which requires Apache support for uwsgi protocol, put
http-socket = 0.0.0.0:8000
which will tell uwsgi to listen on TCP port 8000 and in Apache, use
ProxyPass /mailman3 http://127.0.0.1:8000
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan