[Mailman-Users] Pls help debug mm-postfix disconnect. Thanks.

[Mark Sapiro]

Hugh Esco wrote:

>I vetted the held message and it was posted to the archives,
>but still no message sent to the listmembers.
>
>[06:23:22]<root at www1:/u/d/devmm/mailman> ls logs/ -lt
>total 32
>-rw-rw-r--  1 devmm  devmm  244 Feb 13 14:06 vette
>-rw-rw-r--  1 devmm  devmm 3955 Feb  9 15:42 error
>-rw-rw-r--  1 apache devmm 3543 Jan  8 00:52 subscribe
>-rw-rw-r--  1 devmm  devmm   89 Dec 21 14:53 bounce
>-rw-rw-r--  1 devmm  devmm  172 Dec 21 14:38 post
>-rw-rw-r--  1 devmm  devmm 3339 Dec 21 14:38 qrunner
>-rw-rw-r--  1 devmm  devmm  141 Dec 21 14:38 smtp
>-rw-rw-r--  1 devmm  devmm  580 Dec 21 14:38 smtp-failure
>
>[06:27:57]<root at www1:/u/d/devmm/mailman> ls qfiles/out/ | wc -l
>118


So it looks like you have a huge backlog in the out queue. Look at
what's actually in the 'smtp' log, but that probably won't help
because it hasn't been written since Dec 21. In fact it appears that
nothing has been sent from Mailman since Dec 21, including any
list-owner notifications of held messages. I suspect OutgoingRunner
hasn't been running since then. What's in the qrunner log?

Do

ps -fAw | grep python

or however you spell it on your system to see what qrunners are running.

bin/mailmanctl stop

followed by

bin/mailmanctl start

might get things going.



>Seems to me things are stuck in the outbound que before they 
>get to postfix.  My tests were run today.


Yes, it seems that way to me too.

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