Piet Barber via Mailman-users writes:
However, when I follow the systemctl startup scripts as per the instructions at the URL above, it get stuck in the startup ... forever
What makes you think it's stuck? Have you actually tried to use it? If not, it's probably just that systemd messages were not written to be understood by ordinary mortals.
root@arcus:/etc/nginx# systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: activating (start) since Wed 2025-08-13 23:12:05 UTC; 29s ago
I don't know what the above line is intended to mean. I guess it is some sort of systemd internal concept saying that the application is started and systemd may need to pay attention to it.
Process: 49024 ExecStart=/opt/mailman/venv/bin/mailman start(code=exited, status=0/SUCCESS)
This is normal. The mailman command starts the "master" runner (= daemon) that supervises the application, then exits. In fact, it usually complains that it can't find the PID file. Maybe systemd has gotten smarter about that.
Tasks: 17 (limit: 4605)
That seems right; by default Mailman starts that many processes.
Memory: 878.0M (peak: 878.5M)
That seems right, or maybe a little small.
CPU: 11.030s
That seems like a lot but I've never paid attention to these parts of systemctl status output.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan