[Mailman-Users] locks, max cpu, postfix, qrunner ugliness

[Charlie Watts]

On Sun, 17 Feb 2002, Morgan Fletcher wrote:
> Charlie Watts <cewatts at frontier.net> writes:
> > Anyway, I'd ktrace/strace that python instance, see what it's doing. And
> > look in your mail logs - is it actively dumping things into postfix, or
> > has it not even gotten there, or has it started and paused?
> >
> > Is python just sitting there busy-waiting?
>
> I 'ktrace -dp pid', waited five minutes, did 'ktrace -c', then 'kdump |
> less'.
<snip ktrace output with qrunner busy-waiting>

Try taking qrunner out of cron, sending a message to the list, and
starting qrunner under ktrace. Then do the 'kdump | less' and you should
be able to see where it changes to busy-waiting ...

Is it a lock issue?

> I also should mention that I tested this mailman installation for about
> a month with a small list (~30 addresses) with no problems, and for
> about a week with a larger list (~400 addresses), also with no problems.
> Both those lists contained valid addresses. We did test subscribing an
> address to the second list, then removing the user that was subscribed
> at the user's host, and mailman successfully unsubscribed it after it
> bounced for a while.
>
> Now the 1800-member list is generating a ton of bounces, and I have a
> feeling that's what's choking qrunner. But I may have been biased by
> reading this:
>
> http://sourceforge.net/tracker/?group_id=103&atid=100103&func=detail&aid=449550

Probably not quite the same - in that, qrunner is -dying-. Yours is just
spinning its wheels.

Hrm. I've got 11k users in a list, and know of folks with 100k user lists.

-- 
Charlie Watts
cewatts at frontier.net
Frontier Internet, Inc.
http://www.frontier.net/