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|619270043958240354' 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 start command as the mailman user. I
suspect this is a Fedora issue. I note that
https://docs.fedoraproject.org/en-US/quick-docs/understanding-and-administer...
does not mention User or Group. You might try replacing
ExecStart=/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 stop
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan