[Mailman-Users] problems with bounce processing

[Christopher Adams]

Mark,

I had restarted Mailman several times and still, bounce processing was not
taking place and the bounce log had not been written since 11/13. Before I
left last night, I restarted it and then I noticed a flurry of activity,
with queued bounces being processed. I hadn't looked in the
/qfiles/bounces/ until this morning. Now I see that there is nothing
queued.

So, any idea of what might of happened to gum it up. Thanks for taking the
time to address this issue. It seemingly has corrected itself.



On Tue, Nov 19, 2013 at 4:22 PM, Mark Sapiro <mark at msapiro.net> wrote:

> On 11/19/2013 03:35 PM, Christopher Adams wrote:
> > There is no bounce score entry in the bounce log. As it turns out, there
> > has not been a bounce log generated since 11/13.
> >
> > Would BounceRunner show in a list of processes. If so, I don't see it.
>
> ps -fwC python
>
> or
>
> ps -fwu mailman
>
> should show all the qrunners with the commands that invoked them
> (including the runner name).
>
> e.g.
> $  ps -fwu mailman
> UID        PID  PPID  C STIME TTY          TIME CMD
> mailman  21122     1  0 Nov18 ?        00:00:00 /usr/bin/python2.7
> /usr/local/mailman/bin/mailmanctl -s -q start
> mailman  21123 21122  0 Nov18 ?        00:00:03 /usr/bin/python2.7
> /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
> mailman  21124 21122  0 Nov18 ?        00:00:00 /usr/bin/python2.7
> /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
> mailman  21125 21122  0 Nov18 ?        00:00:00 /usr/bin/python2.7
> /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
> mailman  21126 21122  0 Nov18 ?        00:00:00 /usr/bin/python2.7
> /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
> mailman  21127 21122  0 Nov18 ?        00:00:00 /usr/bin/python2.7
> /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
> mailman  21128 21122  0 Nov18 ?        00:00:08 /usr/bin/python2.7
> /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
> mailman  21129 21122  0 Nov18 ?        00:00:00 /usr/bin/python2.7
> /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
> mailman  21130 21122  0 Nov18 ?        00:00:00 /usr/bin/python2.7
> /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
>
> If BounceRunner isn't running (since 11/13?) that would explain a lot.
>
>
> > Here is an entry in the qrunner log related to BounceRunner:
> >
> > Nov 19 04:02:36 2012 (29791) Master qrunner detected subprocess exit
> > (pid: 27168, sig: None, sts: 2, class: BounceRunner, slice: 1/1)
> > [restarting]
>
>
> What happens daily at 04:02? Check your cron logs or /etc/cron.daily
>
> sts: 2 could be a missing file or directory, but there should be an
> entry in Mailman's error log from the same time.
>
> Are there queued bounces in the bounces queue (Mailman's qfiles/bounces/
> or wherever your package puts it (e.g. /var/spool/mailman/bounces in the
> RedHat/CentOS package).
>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
>



-- 
Christopher Adams
adamsca at gmail.com