Odhiambo Washington via Mailman-users writes: > > connect to Unix domain socket */run/mailman3-web/uwsgi.sock* > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > uwsgi running outside virtualenv??
I don't think that's a problem, unless also running in a chroot, which would be confusing no matter where uswgi is running. "Cannot connect" might mean - uwsgi is running chrooted, and mailman-web should be looking in /path/to/chroot/run/mailman3-web/uwsgi.sock (mentioned first only because I have chroot on the brain because Debian Postfix config) - uwsgi isn't running (this is my bet, because all the mailman-web URLs except mailman3/ were working and they all go through that socket -- I bet they're not working now!) - /run/mailman3-web/uwsgi.sock got deleted - /run/mailman3-web/uwsgi.sock got wrong permissions - the socket is actually /run/mailman3_web/uwsgi.sock or similar (with an underscore!) and mailman-web is misconfigured But as Mark said, the problem you have with "mailman3/" is urls.py. Personally, I think you *should* do the things that Mark said are unnecessary. He's right, but I strongly prefer to keep all my changes to default configuration in one place, and that's /etc/mailman3 for you if I recall correctly. The very fact that you have /etc/mailman3/urls.py screams "I have changed this file" and that's often useful. Steve _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-le...@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/PTP6O46AIM37QNI6ER53SI72JEJFLUPI/ This message sent to arch...@mail-archive.com
