[Mailman-Users] Messages got stuck in "in" queue due to one"bad"message

[Mark Sapiro]

Xueshan Feng wrote:

>On Tue, 2007-02-20 at 15:37 -0800, Mark Sapiro wrote:
>> Xueshan Feng wrote:
>> 
>> Actually, If I understand the situation correctly, IncomingRunner will
>> not be running. It will die and be restarted, but after the 10th
>> restart/die, it won't restart again (but this seems incorrect - see
>> below).
>
>The qrunner log shows they died, but if I do ps -ef |grep
>IncomingRunner, they are still there. 


All four of them?


>> >3. Can the mailman recover itself without human intervention? 
>
>> I don't understand why the message didn't shunt.


I understand why the message didn't shunt. See Stephen's post and my
reply in this thread.


>> Why more than 10 restarts?
>
>Hmm, that's 11. I don't know. The following line followed the 11th
>restarting:
>
>Feb 20 07:55:55 2007 (27933) Qrunner IncomingRunner reached maximum
>restart limit of 10, not restarting.


Maybe it counts from zero and gets 11. It looks OK. It reached the
limit and didn't restart, but there should only have been the 3
remaining IncomingRunners, not four when you looked.


>Thanks a lot! The problem is fixed after the Mailman's own
>pythonlib/email is installed.


There are still some remaining Runner issues. These will all be cleaned
up in Mailman 2.1.10. In the mean time, I may release a patch after I
fully work out what to do.

The bottom line is this error should not have caused the IncomingRunner
to die, and it should not have been looping on the bad message. These
will be fixed.

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