On 5/31/23 22:49, justfixit@marilynstrother.com wrote:
FWIW, looking back at this time period in mailman.log the only instances of "runner exiting" are in groups, at the times when I had manually issued "mailman restart" to try a few different debug logging options. I.e. there was no single / multiple record of "runner exiting" from e.g. an unexpected program fault.
When you issued a restart and the logs show runners restarting, did all
the runners restart or was one or more missing. If you grep the log for
runner started, you should see groups of messages like
Jun 01 08:00:27 2023 (21930) in runner started. Jun 01 08:00:27 2023 (21938) virgin runner started. Jun 01 08:00:28 2023 (21932) bounces runner started. Jun 01 08:00:28 2023 (21935) command runner started. Jun 01 08:00:28 2023 (21941) retry runner started. Jun 01 08:00:28 2023 (21934) archive runner started. Jun 01 08:00:28 2023 (21931) lmtp runner started. Jun 01 08:00:28 2023 (21942) pipeline runner started. Jun 01 08:00:29 2023 (21939) out runner started. Jun 01 08:00:29 2023 (21936) digest runner started. Jun 01 08:00:29 2023 (21937) nntp runner started. Jun 01 08:00:30 2023 (21940) task runner started.
and if any runners are sliced, there will be multiple entries for that
runner, one per slice. Also, because of the way the rest runner is
run, it will be in the list on a start but not on a restart.
If a runner had previously died so it was not running when you did the
restart, it won't be started and will be missing from the above list. In
order to restart runners which have died, you need to do mailman stop
followed by mailman start as opposed to mailman restart
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan