Dennis Putnam via Mailman-users writes:
$ ls /opt/mailman/venv/lib/python3.12/site-packages/gunicorn app� � � � �debug.py� � �http� � � � �__main__.py� reloader.py util.py arbiter.py� errors.py� � __init__.py� pidfile.py� �sock.py workers config.py� �glogging.py� instrument� �__pycache__� systemd.py
That looks OK. Are all the files readable by the mailman user?
Is it possible that mailman-web was installed somewhere other than that virtual environment?
Do I need to specify a path somewhere?
Not if you follow this procedure (note: assumes venv already exists and Mailman core was installed into the venv):
- cd /opt/mailman
- sudo su mailman # or somehow be the mailman user
- . venv/bin/activate
- python -m pip install mailmanweb # maybe that's mailman-web
The point of activating the venv is that the installation process will ensure that the Python installation in the venv is referenced by all packages installed in the venv.
You should ensure that all of the executable paths in the systemd mailman (or mailman3) and mailman-web unit files are absolute paths pointing into the venv.
*I think the main thing is the MySQL stuff in settings.py:
<venv> pip install pymysql
Add lines:
import pymysql pymysql.install_as_MySQLdb()
At least so far.*
Thank you! That's useful.
Steve
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan