On 09/02/2017 12:30 PM, Barry Warsaw wrote:
> 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?
It appears to be in Mailman. I added some logg
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 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
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) nnt
