[Mailman-Users] mailman python-2.4 using 96% cpu

[Goodman, William]

I apologize Mark...

This is the output of:

# ls -aR /opt/software/mailman/qfiles/
/opt/software/mailman/qfiles/:
.  ..  archive  bounces  commands  in  news  out  retry  shunt  virgin

/opt/software/mailman/qfiles/archive:
.  ..

/opt/software/mailman/qfiles/bounces:
.
..
1234190987.539598+fd6c983022fae575bb19abe36c1eb9c9e4d7a896.pck
1234190987.546752+fe6f1ad1df8e2079ccb23fc3cfeeff4fd5441082.pck
1234190987.7204871+3a2c234edd8b221eaca05854a5dfd5162c58f6da.pck
1234190987.960499+c00b2d2522ee0d1246583d41a3323958520da746.pck
1234190988.063931+b4b96d43770f9f37a42f57ad50055c8837b21874.pck
1234190988.3409979+4f2d8e7a9fc7810110611d42fd82f57c167dbc1c.pck
1234190988.366761+dab73d1f6982797f201613fd4b60237b4e01bab3.pck
1234190988.669873+d4e730813b15eb5a7a3c427183808d07fb0b7ca4.pck
1234190988.7999749+9e225d8f549d8f35a9a4255c572ac88f6bd5c845.pck
1234190988.961921+417ad154e340bd2947ed5df80c530ab697d7a17a.pck.tmp

/opt/software/mailman/qfiles/commands:
.  ..

/opt/software/mailman/qfiles/in:
.
..
1234190978.5258429+b87a7a844ad37ebb49d0724f57432f96a184db71.bak
1234190978.5667651+ed691242dad999eb51ccc8fab3343b6619856592.pck
1234190978.6760139+e4f48d142e1cb482489bebd1027e9b550915dc55.pck
1234190988.577697+6801e46df1e6c7432b7f9e458ef424bf28792659.pck

/opt/software/mailman/qfiles/news:
.  ..

/opt/software/mailman/qfiles/out:
.   1234190978.3703849+eed96b821c17c2186fc25541469e5ef0c0af6a47.pck
..  1234190978.738651+91bcf5af1bdaac8c799b378c3b1301b10a53252c.bak

/opt/software/mailman/qfiles/retry:
.  ..

/opt/software/mailman/qfiles/shunt:
.  ..

/opt/software/mailman/qfiles/virgin:
.  .. 

-----Original Message-----
From: Mark Sapiro [mailto:mark at msapiro.net] 
Sent: Friday, February 06, 2009 8:05 PM
To: Goodman, William; mailman-users at python.org
Subject: RE: [Mailman-Users] mailman python-2.4 using 96% cpu

Goodman, William wrote:

>Cool Mike that helped a lot...


It's Mark ...


>I was so frustrated I set it to:
>
>QRUNNER_SLEEP_TIME = seconds(10)
>
>That seem to calm it down a bit.
>
>top - 18:38:02 up 56 min,  2 users,  load average: 1.25, 1.20, 1.83
>Tasks: 109 total,   1 running, 108 sleeping,   0 stopped,   0 zombie
>Cpu(s): 20.3%us,  0.3%sy,  0.0%ni, 79.2%id,  0.2%wa,  0.0%hi,  0.0%si, 
>0.0%st
>Mem:   3866604k total,   494800k used,  3371804k free,   175632k
buffers
>Swap:  4194296k total,        0k used,  4194296k free,   172108k cached
>
>  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
>19021 mailman   25   0  150m  12m 2752 S   41  0.3   1:59.92 python2.4
>    8 root      10  -5     0    0    0 S    0  0.0   0:03.72 events/0
>19797 root      16   0 12584 1068  800 S    0  0.0   0:00.30 top
>    1 root      15   0 10324  692  580 S    0  0.0   0:00.40 init
>
>But I still see 99% spikes from time to time. Is there a BOUNCERUNNER 
>and INCOMINGRUNNER parameter?


QRUNNER_SLEEP_TIME applies to all the runners.


I suppose it's possible you are just being bombarded with mail. Perhaps
there is some kind of mail loop.

What's in Mailman's vette log?

What do you see if you stop Mailman and while it is stopped do

ls -aR qfiles/

Do you see any entries? If so, and you do the ls again are there more
entries or the same ones? If there are entries, what's in them (use
bin/show_qfiles to list them)?

Also, as root do

strace -p xxx -o filename

where xxx is the pid of incoming runner. Let it run for 10 or 20 seconds
and then stop it with control-C and see what's in the output (filename).

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