On 3/29/19 2:28 PM, Dmitry Makovey wrote:
I've had encountered this situation now twice: mail is being stuck in "out" queue and nothing in the logs indicates the issue. Is there a way to ask mailman-core politely to attempt delivery (perhaps with increased debugging in the logs) *without* restarting the core (which does solve *this* problem but creates other problems, like availability of the mailman as a whole)
Is the "out" runner running?
ps -fwwA |grep runner=out
If not, you should be able to start it as the Mailman user with a command like
/path/to/python3 /path/to/mailman/bin/runner -C /path/to/mailman.cfg --runner=out:0:1
See 'ps -fwwA|grep runner' for examples.
If the out runner is running, is there a file named *.bak along with all the *.pck files in queue/out/
And if it's not, is there anything in Mailman's logs to indicate why it died?
Also, 'mailman restart' should only take a matter of seconds, but if the out runner is running but not processing its queue, I think sending it a SIGINT should restart it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan