It would be interesting to know if the problem is in the init script or Mailman. You may have to crank up logging of both to find out. Also, I wonder if the same problem occurs if you use systemd?
Other than that I don’t have any ideas.
-Barry
On Sep 2, 2017, at 13:31, Mark Sapiro <mark@msapiro.net> wrote:
On 09/02/2017 08:50 AM, Mark Sapiro wrote:
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).
The issue seems unrelated to qcluster. As a test, I stopped qcluster, removed /etc/init.d/qcluster and the /etc/rc*.d entries and rebooted the server and mailman still wasn't started on reboot.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/barry%40list.org
Security Policy: http://wiki.list.org/x/QIA9