I have this in my mailman3.service file:
[Service] Type=forking PIDFile=/opt/mailman/mm/var/master.pid Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" User=mailman Group=mailman ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop That works fine.
Am Dienstag, 25. Oktober 2022, 07:06:57 CEST schrieb Onyeibo Oku:
On Sun, 23 Oct 2022 08:00:19 -0700
Mark Sapiro <mark@msapiro.net> wrote:
On 10/22/22 21:29, Onyeibo Oku wrote:
Now Mailman starts, and stops as desired when running as mailman user (both in virtual and non-virtual environments). However, running the service via systemd still fails. I now get a different traceback:
Oct 23 03:43:00 mail.server.tld mailman[19410]: Traceback (most
recent call last): ...
Oct 23 03:43:00 mail.server.tld mailman[19410]: with open(self._claimfile, 'w') as fp: Oct 23 03:43:00 mail.server.tld mailman[19410]: PermissionError: [Errno 13] Permission denied: '/opt/mailman/mm/var/locks/mailman-cfg.lck|server.tld|19410|619270043958 240354' Oct 23 03:43:00 mail.server.tld systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE
What are ownership and permissions on /opt/mailman/mm/var/locks/
Assuming they are
drwxr-xr-x mailman mailman
it must be the case that systemd is not running the
/opt/mailman/venv/bin/mailman startcommand as themailmanuser. I suspect this is a Fedora issue. I note that https://docs.fedoraproject.org/en-US/quick-docs/understanding-and-administ ering-systemd/#_service_parameters does not mention User or Group. You might try replacingExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop with ExecStart=sudo -u mailman /opt/mailman/venv/bin/mailman start ExecReload=sudo -u mailman /opt/mailman/venv/bin/mailman restart ExecStop=sudo -u mailman /opt/mailman/venv/bin/mailman stopThis does not work. Systemd says it cannot find sudo (file). After updating in the commands "sudo" to "/bin/sudo" afterwards Systemd throws a different error message: PermissionError on /bin/sudo
This is tiring. At this moment I am left with the possibility that SELinux may be in the way. I cannot think of a way to prove this hypothesis. This is speculation. Perhaps I should try another installation method other than Virtual. I found Mailman3 in Fedora repository. Yes, it is packaged. May be I should try that or perhaps I should try the git version. I'd be happy to have a functioning Mailman before Friday.
Regards Onyeibo
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/