What is in the logs about why the locks remain? There should be something in the system log about it if systemd kills a service process because it doesn't stop in time during shutdown... -Gerald
On 21.06.26 13:16, Lars Bjørndal wrote:
Sometimes when I reboot the machine, I experience that mailman doesn't start because the files /opt/mailman3/mm/var/locks/master.lck* isn't deleted during shutdown. Maybe one way to solve this could be to use ExecStartPre directive in the systemd service to remove the lock files. What's the best practice to solve this problem? BTW I've noticed that doing
systemctl stop mailman3takes a very long time, 45 secs. or something like that.
Mailman 3.3.10
Python 3.12.13
[Unit] Description=GNU Mailing List Manager After=syslog.target network.target postgresql.service [Service] Type=forking PIDFile=/opt/mailman3/mm/var/master.pid User=mailman3 Group=mailman3 Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" ExecStart=/opt/mailman3/venv/bin/mailman start ExecReload=/opt/mailman3/venv/bin/mailman restart ExecStop=/opt/mailman3/venv/bin/mailman stop # Tested, but have no effect on deletion of the lock file. #Restart=on-failure #RestartSec=15 [Install] WantedBy=multi-user.targetLars
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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to vogt@spamcop.net