On 8/9/21 8:56 AM, Richard Rosner wrote:
Mark Sapiro wrote:
The REST API is apparently not listening on the host/port this is trying to connest to.
Apparently. The question is why.
You are in a better position to answer that than am I.
What does sudo netstat -lntp show?
What does ps -fwwa|grep rest show?
What is executing the manage.py command to start Django. Is it user list?
Probably. It depends on who is calling it. I understand too little of the new architecture. But mailman3.service is run as list, mailman3-web.service as root.
mailman3-web.service must also run as list.
I don't use uwsgi and know little about it so I don't know what the Unix domain socket /run/mailman3-web/uwsgi.sock connection is for, but this appears to be some miscunfiguration between apache and uwsgi. Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via tcp port 8000 and uwsgi is configured with [uwsgi] uwsgi-socket = 0.0.0.0:8000
I too have no experience in the combination ow apache and uwsgi. The only other uwsgi app I'm running is on another server and running under nginx.
So, what do you have in your apache config for proxying to uwsgi and what's your uwsgi configuration.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan