[Mailman-Users] Uncaught runner exception

[Mark Sapiro]

On 3/8/19 12:05 AM, Lothar Schilling wrote:
> Am 07.03.2019 um 23:54 schrieb Mark Sapiro:
>>
>> You can now reprocess them and add them to the archive by running
>> Mailman's 'bin/unshunt' command.
> Oh, that's what I did, unshunting them. They were processed and
> archived. But the messages - almost 1.000 - are still queued. Should/can
> I safely delete them?

Normally, bin/unshunt removes the .pck files from the shunt queue and
requeues them to the original queue. If they reappear in qfiles/shunt/
it's because reprocessing them threw another exception. There should be
error messages in Mailman's error log with tracebacks and "shunting"
messages.  Are there such messages and if so, what are they. Also, do
the files in qfiles/shunt have new timestamps?


>> I would still like to find the underlying issue. I have been unable to
>> duplicate it locally. I would appreciate it if before you run
>> bin/unshunt, you could copy a few of the .pck files aside and send them
>> to me off-list.
> Will send some .pck files to your private address. Some may hold content
> which is not meant to be publicly available, they are for your eyes only :-)


Thank you. I will treat them confidentially.

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