On 12/28/21 1:20 PM, Mark Sapiro wrote:
It looks to me like the timeout is in stopping, not starting. What happens if you separately
systemctl stop mailmanweb
and
systemctl start mailmanweb
Confirmed:
root@myhost:/etc/mailman3# time systemctl stop mailmanweb
real 1m30.239s user 0m0.010s sys 0m0.004s root@myhost:/etc/mailman3# time systemctl start mailmanweb
real 0m0.012s user 0m0.011s sys 0m0.001s
On 12/28/21 3:01 PM, Mark Sapiro wrote:
Is your /etc/systemd/system/mailmanweb.service the recommended one at
https://docs.mailman3.org/en/latest/install/virtualenv.html#automatically-st...
Yes, modulo the use of MariaDB instead of PostgreSQL.
If so, try adding
KillSignal=SIGQUIT
to the Service section and see if that fixes it.
root@myhost:/etc/mailman3# time systemctl restart mailmanweb
real 0m1.026s user 0m0.008s sys 0m0.004s
My limited understanding of SIGQUIT is that it dumps core, but 'find / -type f -name '*.core' did not return any core dumps from this event.
Still unsure why the service hung on stop, but thanks!
dn