On 7/29/20 10:16 AM, Abhijith PA via Mailman-users wrote:
When I restarted mailman. I got,
Jul 29 16:58:21 2020 (14473) SHUNTING: 1596041901.2833998+efbeb949a9c248bae23ea6bcc644450f497a4d8d
I think Mailman's var/ directory in the Debian package is /var/lib/mailman3/, so what does
ls -aR /var/lib/mailman3/queueshow? Is there a .pck file either in shunt/ or in out/?There is many .pck files in /var/lib/mailman3/queue/shunt and /var/lib/mailman3/queue/out. And a lot of .psv files in /var/lib/mailman3/queue/bad
The .pck and (presumably one) .bak files in queue/out are messages waiting to be processed by out runner, the .bak is the one currently being processed. It appears your out queue is backlogged, but that is a separate issue and may just be transient.
For every message in queue/shunt there should be a SHUNTING message and also an exception with Traceback logged in mailman.log. It is these Tracebacks we need to see to know what the issue might be. (If they're all the same exception, we only need one.)
The .psv files in queue/bad are unparseable messages. There should be a
"Skipping and preserving unparseable message:" entry in mailman.log for
each of these. The messages can be seen with mailman qfile pointing to
the .psv file. If they look like legitimate messages, it is possible a
permissions issue that caused them to be unparseable.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan