On 1/25/22 2:59 PM, gordon@dickens.com wrote:
Thanks to David and everybody else that have replied to my problem. I have proceeded to uninstall the debian mailman3 packages and then endeavored to install everything with venv. I have implemented all of David's configuration suggestions which were very helpful. Now, mailman3 (core) appears to be working properly in that I can start/stop/restart/status the service. Also, the command "mailman info" from the venv prompt yields output which appears to be correct and the same as in the venv instructions. However, I have not been able to get mailman3-web working.
One general comment: Debian packages install files with a different owner than the pip install. You want to be sure all your directories and files are owned by the Mailman user ('mailman' on Debian).
All of my configuration files may be viewed here:
https://dickens.com/etc-mailman3/
The above files are basically a mirror of the contents of my /etc/mailman3 directory except that I have obfuscated sensitive info such as keys, passwords and email addresses.
Executing the mailman3-web service script with the command "systemctl start mailman3-web" starts everything without errors, however, the command "systemctl status mailman3-web" then generates the following output with errors:
● mailman3-web.service - GNU Mailman Web UI Loaded: loaded (/etc/mailman3/mailman3-web.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-01-25 17:10:30 EST; 6s ago Process: 1718478 ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini (code=exited, status=1/FAILURE) Main PID: 1718478 (code=exited, status=1/FAILURE) CPU: 12ms
Jan 25 17:10:29 slc.mailhub4u.com systemd[1]: Started GNU Mailman Web UI. Jan 25 17:10:30 slc.mailhub4u.com uwsgi[1718478]: [uWSGI] getting INI configuration from /etc/mailman3/uwsgi.ini Jan 25 17:10:30 slc.mailhub4u.com systemd[1]: mailman3-web.service: Main process exited, code=exited, status=1/FAILURE Jan 25 17:10:30 slc.mailhub4u.com systemd[1]: mailman3-web.service: Failed with result 'exit-code'.
Also, /var/log/syslog and "journalctl | grep mailman3-web" contain these two lines of errors:
Jan 25 14:00:46 slc systemd[1]: mailman3-web.service: Main process exited, code=exited, status=1/FAILURE Jan 25 14:00:46 slc systemd[1]: mailman3-web.service: Failed with result 'exit-code'.
Do you have anything further in any of the logs in /opt/mailman/web/logs ?
Also, other commands in the venv instructions do not work such as "mailman-web migrate" which produces volumes of error dialog starting with:
Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site-packages/django/template/utils.py", line 66, in __getitem__ return self._engines[alias] KeyError: 'django'
This one might be due to a bug I hit as well. There's a problem with mistune, one of the components. If that's the issue here, this should address it, run as the mailman user:
pip install mistune==2.0.0rc1 mailman-web migrate mailman-web compress mailman-web collectstatic mailman-web compilemessages
dn