I have encountered a strange issue on both lists.mailman3.org and mail.python.org. Namely, Mailman3 is not started upon reboot.
If I reboot the server Mailman 3 is shut down normally but is never started when the server comes up. A typical mailman.log excerpt is
Sep 02 10:12:06 2017 (20345) nntp runner caught SIGTERM. Stopping. Sep 02 10:12:06 2017 (20345) %s runner exiting. Sep 02 10:12:06 2017 (20342) command runner caught SIGTERM. Stopping. Sep 02 10:12:06 2017 (20342) %s runner exiting. Sep 02 10:12:07 2017 (20348) %s runner exiting. Sep 02 10:12:07 2017 (20318) Master stopped Sep 02 10:21:24 2017 (17278) Master started Sep 02 10:21:29 2017 (17306) %s runner started. Sep 02 10:21:29 2017 (17301) %s runner started. Sep 02 10:21:29 2017 (17311) %s runner started. Sep 02 10:21:29 2017 (17299) %s runner started.
(the '%s' should be fixed by https://gitlab.com/mailman/mailman/merge_requests/311). The entries from 10:12:07 are the normal shutdown from the reboot. The very next thing is at 10:21:24 when I manually did 'service mailman start'. The /etc/init.d/mailman3 script is attached as mailman.txt. This has not changed recently. The only thing that has changed is the /etc/init.d/qcluster script (attached as qcluster.txt). This existed before, but was changed to use start-stop-daemon and to add a 'stop' function.
I also did 'update-rc.d qcluster defaults' to create the rc*.d entries for qcluster which I had neglected to do before. The entries for mailman3 are there (unchanged in over a year).
Does anyone have an idea why Mailman 3 is not starting on reboot?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan