[Mailman-Users] Mailman 2.1.23: Issues with mailmanctl restart

[Mark Sapiro]

> On 06/20/2017 07:12 AM, Frank Lanitz wrote:
>> 
>> I have seen recently issues with mailmanctl restart: From time to time
>> there seems to be some kind of race condition between shutdown and
>> startup. Inside qrunner log it looks something like — but not started.
>> 
>> Jun 18 02:20:21 2017 (30372) OutgoingRunner qrunner caught SIGTERM. 
>> Stopping.
>> Jun 18 02:20:21 2017 (30368) BounceRunner qrunner caught SIGTERM. 
>> Stopping.
>> Jun 18 02:20:21 2017 (30368) BounceRunner qrunner exiting.
>> Jun 18 02:20:21 2017 (30372) OutgoingRunner qrunner exiting.
>> Jun 18 02:20:21 2017 (30370) IncomingRunner qrunner caught SIGTERM. 
>> Stopping.
>> Jun 18 02:20:22 2017 (30370) IncomingRunner qrunner exiting.
>> Jun 18 02:20:21 2017 (30373) VirginRunner qrunner caught SIGTERM. 
>> Stopping.
>> Jun 18 02:20:22 2017 (30367) ArchRunner qrunner caught SIGTERM.  Stopping.
>> Jun 18 02:20:22 2017 (30367) ArchRunner qrunner exiting.
>> Jun 18 02:20:22 2017 (30369) CommandRunner qrunner caught SIGTERM. 
>> Stopping.
>> Jun 18 02:20:22 2017 (30373) VirginRunner qrunner exiting.
>> Jun 18 02:20:22 2017 (30369) CommandRunner qrunner exiting.
>> Jun 18 02:20:22 2017 (30371) NewsRunner qrunner caught SIGTERM.  Stopping.
>> Jun 18 02:20:24 2017 (30371) NewsRunner qrunner exiting.
>> Jun 18 02:20:22 2017 (30374) RetryRunner qrunner caught SIGTERM.  Stopping.
>> Jun 18 02:20:25 2017 (30374) RetryRunner qrunner exiting.


Also, in addition to my prior reply, note that "restart" should be
sending SIGINT to the runners, not SIGTERM

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan