subject:"Re\: \[Mailman\-Users\] mailman python\-2.4 using 96% cpu"

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

2009-02-10 Thread Mark Sapiro

Mark Sapiro wrote:

>Goodman, William wrote:
>
>>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
>
>
>You are in the process of queueing one bounce, and 9 other bounces have
>arrived in the last 1.4 seconds.
>
>
>>/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
>
>
>You are processing one incoming message and 3 other messages have
>arrived within 1 second of that one.
>
>
>>/opt/software/mailman/qfiles/news:
>>.  ..
>>
>>/opt/software/mailman/qfiles/out:
>>.   1234190978.3703849+eed96b821c17c2186fc25541469e5ef0c0af6a47.pck
>>..  1234190978.738651+91bcf5af1bdaac8c799b378c3b1301b10a53252c.bak
>
>
>You are processing one outgoing message and another is waiting which
>from within a fraction of a second.
>
>
>>/opt/software/mailman/qfiles/retry:
>>.  ..
>>
>>/opt/software/mailman/qfiles/shunt:
>>.  ..
>>
>>/opt/software/mailman/qfiles/virgin:
>>.  .. 
>
>
>It looks to me like you are being hit with massive amounts of spam to
>the list's post and bounces address or you have some kind of mail loop
>going on which is generating all this mail.
>
>Your high CPU utilization is a result of Mailman doing real work to
>handle all this mail.


After further off-list analysis, it turned out there was a mail loop
involving the mailman-owner address. Here's the OP's description.

This was the case:

I moved the lists server from one hosts to another (which I wouldn't
recommend us less you have no choice)
The original host was using sendmail, the new host is using Postfix
(easy to deal with). When I tarred up
the lists I forgot that mailman is a lists, so the configuration for the
original server could find a valid
email address for the owner, it was looking at the original servers
mailman email address which was a different domain. This cause the
exchange server to send the mail back to the host, then the host would
send it back to
the exchange server and so on ...


-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

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

2009-02-09 Thread Mark Sapiro

Goodman, William wrote:

>I apologize Mark...


Thanks. No problem.


>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


You are in the process of queueing one bounce, and 9 other bounces have
arrived in the last 1.4 seconds.


>/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


You are processing one incoming message and 3 other messages have
arrived within 1 second of that one.


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


You are processing one outgoing message and another is waiting which
from within a fraction of a second.


>/opt/software/mailman/qfiles/retry:
>.  ..
>
>/opt/software/mailman/qfiles/shunt:
>.  ..
>
>/opt/software/mailman/qfiles/virgin:
>.  .. 


It looks to me like you are being hit with massive amounts of spam to
the list's post and bounces address or you have some kind of mail loop
going on which is generating all this mail.

Your high CPU utilization is a result of Mailman doing real work to
handle all this mail.



Mark Sapiro wrote:
>
>Goodman, William wrote:
>
>I suppose it's possible you are just being bombarded with mail. Perhaps
>there is some kind of mail loop.


See above?


>What's in Mailman's vette log?


??


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


Stop Mailman. (bin/mailmanctl stop)


>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)?


Look at the queue entries with bin/show_qfiles. What kinds of messages
do they contain?


>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).


It's not necessary to do the above since I think I know that there is
not actually a problem with Mailman's relinquishing when it doesn't
have anything to do. The problem is it always has something to do.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

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

2009-02-09 Thread 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:m...@msapiro.net] 
Sent: Friday, February 06, 2009 8:05 PM
To: Goodman, William; mailman-users@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 %MEMTIME+  COMMAND
>19021 mailman   25   0  150m  12m 2752 S   41  0.3   1:59.92 python2.4
>8 root  10  -5 000 S0  0.0   0:03.72 events/0
>19797 root  16   0 12584 1068  800 S0  0.0   0:00.30 top
>1 root  15   0 10324  692  580 S0  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 The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

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

2009-02-06 Thread Mark Sapiro

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 %MEMTIME+  COMMAND
>19021 mailman   25   0  150m  12m 2752 S   41  0.3   1:59.92 python2.4
>8 root  10  -5 000 S0  0.0   0:03.72 events/0
>19797 root  16   0 12584 1068  800 S0  0.0   0:00.30 top
>1 root  15   0 10324  692  580 S0  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 The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

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

2009-02-06 Thread Goodman, William

Cool Mike that helped a lot...

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 %MEMTIME+  COMMAND
19021 mailman   25   0  150m  12m 2752 S   41  0.3   1:59.92 python2.4
8 root  10  -5 000 S0  0.0   0:03.72 events/0
19797 root  16   0 12584 1068  800 S0  0.0   0:00.30 top
1 root  15   0 10324  692  580 S0  0.0   0:00.40 init

But I still see 99% spikes from time to time. Is there a BOUNCERUNNER
and INCOMINGRUNNER parameter?

Bill

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

Goodman, William wrote:

>Sorry to say Mike this is after applying all patches... but it now 
>archiving


OK. That's good.


>top - 16:33:18 up 1 day, 23:08,  2 users,  load average: 2.87, 2.24,
>1.32
>Tasks: 106 total,   3 running, 103 sleeping,   0 stopped,   0 zombie
>Cpu(s): 58.7%us,  3.5%sy,  0.0%ni, 37.4%id,  0.2%wa,  0.0%hi,  0.2%si, 
>0.0%st
>Mem:   3866604k total,  1600176k used,  2266428k free,   442080k
buffers
>Swap:  4194296k total,4k used,  4194292k free,   373852k cached
>
>  PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
> 8969 mailman   25   0  150m  12m 2748 R   93  0.3   5:37.84 python2.4
> 8971 mailman   16   0  147m 9952 2808 S9  0.3   1:42.04 python2.4
> 8967 mailman   16   0  151m  12m 2748 S1  0.3   0:20.62 python2.4
>2 root  RT  -5 000 S0  0.0   0:06.35
migration/0
>10760 postfix   16   0 54212 2624 2064 S0  0.1   0:00.12 local
>10895 postfix   15   0 54252 2356 1820 S0  0.1   0:00.11 cleanup
>
># ps -fwp 8969
>UIDPID  PPID  C STIME TTY  TIME CMD
>mailman   8969  8965 73 16:25 ?00:06:43 /usr/bin/python2.4
>/opt/software/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
>
># ps -fwp 8971
>UIDPID  PPID  C STIME TTY  TIME CMD
>mailman   8971  8965 22 16:25 ?00:02:10 /usr/bin/python2.4
>/opt/software/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
>
># ps -fwp 8967
>UIDPID  PPID  C STIME TTY  TIME CMD
>mailman   8967  8965  4 16:25 ?00:00:28 /usr/bin/python2.4
>/opt/software/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
>
>Any other suggestions are welcomed.


I hope you don't have anything like

QRUNNER_SLEEP_TIME = 0

in mm_cfg.py. It's unlikely that that would cause a pattern like this.
More likely would be all runners using aproximately equal CPU.

You could try putting

QRUNNER_SLEEP_TIME = seconds(5)

in mm_cfg.py (the default is 1) and restarting Mailman to see if that
changes things. If that doesn't help, you may need to strace the PID of
IncomingRunner to see what it's doing. It should be spending almost all
of it's time waiting for

select(0, NULL, NULL, NULL, {1, 0})

(or maybe

select(0, NULL, NULL, NULL, {5, 0})

if you made the QRUNNER_SLEEP_TIME change).

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

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

2009-02-06 Thread Mark Sapiro

Goodman, William wrote:

>Sorry to say Mike this is after applying all patches... but it now
>archiving


OK. That's good.


>top - 16:33:18 up 1 day, 23:08,  2 users,  load average: 2.87, 2.24,
>1.32
>Tasks: 106 total,   3 running, 103 sleeping,   0 stopped,   0 zombie
>Cpu(s): 58.7%us,  3.5%sy,  0.0%ni, 37.4%id,  0.2%wa,  0.0%hi,  0.2%si,
>0.0%st
>Mem:   3866604k total,  1600176k used,  2266428k free,   442080k buffers
>Swap:  4194296k total,4k used,  4194292k free,   373852k cached
>
>  PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
> 8969 mailman   25   0  150m  12m 2748 R   93  0.3   5:37.84 python2.4
> 8971 mailman   16   0  147m 9952 2808 S9  0.3   1:42.04 python2.4
> 8967 mailman   16   0  151m  12m 2748 S1  0.3   0:20.62 python2.4
>2 root  RT  -5 000 S0  0.0   0:06.35 migration/0
>10760 postfix   16   0 54212 2624 2064 S0  0.1   0:00.12 local
>10895 postfix   15   0 54252 2356 1820 S0  0.1   0:00.11 cleanup
>
># ps -fwp 8969
>UIDPID  PPID  C STIME TTY  TIME CMD
>mailman   8969  8965 73 16:25 ?00:06:43 /usr/bin/python2.4
>/opt/software/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s 
>
># ps -fwp 8971
>UIDPID  PPID  C STIME TTY  TIME CMD
>mailman   8971  8965 22 16:25 ?00:02:10 /usr/bin/python2.4
>/opt/software/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
>
># ps -fwp 8967
>UIDPID  PPID  C STIME TTY  TIME CMD
>mailman   8967  8965  4 16:25 ?00:00:28 /usr/bin/python2.4
>/opt/software/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
>
>Any other suggestions are welcomed.


I hope you don't have anything like

QRUNNER_SLEEP_TIME = 0

in mm_cfg.py. It's unlikely that that would cause a pattern like this.
More likely would be all runners using aproximately equal CPU.

You could try putting

QRUNNER_SLEEP_TIME = seconds(5)

in mm_cfg.py (the default is 1) and restarting Mailman to see if that
changes things. If that doesn't help, you may need to strace the PID
of IncomingRunner to see what it's doing. It should be spending almost
all of it's time waiting for

select(0, NULL, NULL, NULL, {1, 0})

(or maybe

select(0, NULL, NULL, NULL, {5, 0})

if you made the QRUNNER_SLEEP_TIME change).

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

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

2009-02-06 Thread Goodman, William

Sorry to say Mike this is after applying all patches... but it now
archiving

top - 16:33:18 up 1 day, 23:08,  2 users,  load average: 2.87, 2.24,
1.32
Tasks: 106 total,   3 running, 103 sleeping,   0 stopped,   0 zombie
Cpu(s): 58.7%us,  3.5%sy,  0.0%ni, 37.4%id,  0.2%wa,  0.0%hi,  0.2%si,
0.0%st
Mem:   3866604k total,  1600176k used,  2266428k free,   442080k buffers
Swap:  4194296k total,4k used,  4194292k free,   373852k cached

  PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
 8969 mailman   25   0  150m  12m 2748 R   93  0.3   5:37.84 python2.4
 8971 mailman   16   0  147m 9952 2808 S9  0.3   1:42.04 python2.4
 8967 mailman   16   0  151m  12m 2748 S1  0.3   0:20.62 python2.4
2 root  RT  -5 000 S0  0.0   0:06.35 migration/0
10760 postfix   16   0 54212 2624 2064 S0  0.1   0:00.12 local
10895 postfix   15   0 54252 2356 1820 S0  0.1   0:00.11 cleanup

# ps -fwp 8969
UIDPID  PPID  C STIME TTY  TIME CMD
mailman   8969  8965 73 16:25 ?00:06:43 /usr/bin/python2.4
/opt/software/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s 

# ps -fwp 8971
UIDPID  PPID  C STIME TTY  TIME CMD
mailman   8971  8965 22 16:25 ?00:02:10 /usr/bin/python2.4
/opt/software/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s

# ps -fwp 8967
UIDPID  PPID  C STIME TTY  TIME CMD
mailman   8967  8965  4 16:25 ?00:00:28 /usr/bin/python2.4
/opt/software/mailman/bin/qrunner --runner=BounceRunner:0:1 -s

Any other suggestions are welcomed.

Bill

-Original Message-
From: mailman-users-bounces+wgoodman=jcvi@python.org
[mailto:mailman-users-bounces+wgoodman=jcvi@python.org] On Behalf Of
Goodman, William
Sent: Thursday, February 05, 2009 4:10 PM
To: Mark Sapiro; mailman-users@python.org
Subject: Re: [Mailman-Users] mailman python-2.4 using 96% cpu

Hi Mike,

Theses are the high cpu grabbers:

mailman   4764  4751 74 Feb04 ?17:00:03 /usr/bin/python2.4
/opt/software/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s

UIDPID  PPID  C STIME TTY  TIME CMD
mailman   4766  4751 22 Feb04 ?05:08:33 /usr/bin/python2.4
/opt/software/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s

UIDPID  PPID  C STIME TTY  TIME CMD
mailman   4760  4751  4 Feb04 ?01:01:34 /usr/bin/python2.4
/opt/software/mailman/bin/qrunner --runner=BounceRunner:0:1 -s 

Also there's a dead like to the patch location you sent me.

Bill

-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Thursday, February 05, 2009 3:47 PM
To: Goodman, William; mailman-users@python.org
Subject: RE: [Mailman-Users] mailman python-2.4 using 96% cpu

Goodman, William wrote:

>What release did you upgrade from?
>>From 2.1.7 to 2.1.12rc1


OK


>What's in Mailman's logs?
[...]
>snipet from error:
>Feb 04 19:13:23 2009 (4759) Traceback (most recent call last):
>  File "/opt/software/mailman/Mailman/Queue/Runner.py", line 120, in 
>_oneloop
>self._onefile(msg, msgdata)
>  File "/opt/software/mailman/Mailman/Queue/Runner.py", line 191, in 
>_onefile
>keepqueued = self._dispose(mlist, msg, msgdata)
>  File "/opt/software/mailman/Mailman/Queue/ArchRunner.py", line 73, in

>_dispose
>mlist.ArchiveMail(msg)
>  File "/opt/software/mailman/Mailman/Archiver/Archiver.py", line 216, 
>in ArchiveMail
>h.processUnixMailbox(f)
>  File "/opt/software/mailman/Mailman/Archiver/pipermail.py", line 564,

>in processUnixMailbox
>m = mbox.next()
>  File "/usr/lib64/python2.4/mailbox.py", line 35, in next
>return self.factory(_Subfile(self.fp, start, stop))
>  File "/opt/software/mailman/Mailman/Mailbox.py", line 89, in scrubber
>return mailbox.scrub(msg)
>  File "/opt/software/mailman/Mailman/Mailbox.py", line 109, in scrub
>return self._scrubber(self._mlist, msg)
>  File "/opt/software/mailman/Mailman/Handlers/Scrubber.py", line 408, 
>in process
>replace_payload_by_text(msg, sep.join(text), charset)
>  File "/opt/software/mailman/Mailman/Handlers/Scrubber.py", line 170, 
>in replace_payload_by_text
>msg.set_payload(text, charset)
>  File "/usr/lib64/python2.4/email/Message.py", line 218, in
set_payload
>self.set_charset(charset)
>  File "/usr/lib64/python2.4/email/Message.py", line 242, in
set_charset
>raise TypeError(charset)
>TypeError: us-ascii


This is a problem in the 2.1.12rc1 release. See the post at
<http://mail.python.org/pipermail/mailman-announce/2009-January/000129.h
tml>
for the fix. There are a couple of other problems too. I will be
releasing 2.1.12rc2 in a day or so.


[...]
>snipet from smtp-failure:
>.org>
>Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@

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

2009-02-06 Thread Goodman, William

Hi Mike,

Theses are the high cpu grabbers:

mailman   4764  4751 74 Feb04 ?17:00:03 /usr/bin/python2.4
/opt/software/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s

UIDPID  PPID  C STIME TTY  TIME CMD
mailman   4766  4751 22 Feb04 ?05:08:33 /usr/bin/python2.4
/opt/software/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s

UIDPID  PPID  C STIME TTY  TIME CMD
mailman   4760  4751  4 Feb04 ?01:01:34 /usr/bin/python2.4
/opt/software/mailman/bin/qrunner --runner=BounceRunner:0:1 -s 

Also there's a dead like to the patch location you sent me.

Bill

-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net] 
Sent: Thursday, February 05, 2009 3:47 PM
To: Goodman, William; mailman-users@python.org
Subject: RE: [Mailman-Users] mailman python-2.4 using 96% cpu

Goodman, William wrote:

>What release did you upgrade from?
>>From 2.1.7 to 2.1.12rc1


OK


>What's in Mailman's logs?
[...]
>snipet from error:
>Feb 04 19:13:23 2009 (4759) Traceback (most recent call last):
>  File "/opt/software/mailman/Mailman/Queue/Runner.py", line 120, in 
>_oneloop
>self._onefile(msg, msgdata)
>  File "/opt/software/mailman/Mailman/Queue/Runner.py", line 191, in 
>_onefile
>keepqueued = self._dispose(mlist, msg, msgdata)
>  File "/opt/software/mailman/Mailman/Queue/ArchRunner.py", line 73, in

>_dispose
>mlist.ArchiveMail(msg)
>  File "/opt/software/mailman/Mailman/Archiver/Archiver.py", line 216, 
>in ArchiveMail
>h.processUnixMailbox(f)
>  File "/opt/software/mailman/Mailman/Archiver/pipermail.py", line 564,

>in processUnixMailbox
>m = mbox.next()
>  File "/usr/lib64/python2.4/mailbox.py", line 35, in next
>return self.factory(_Subfile(self.fp, start, stop))
>  File "/opt/software/mailman/Mailman/Mailbox.py", line 89, in scrubber
>return mailbox.scrub(msg)
>  File "/opt/software/mailman/Mailman/Mailbox.py", line 109, in scrub
>return self._scrubber(self._mlist, msg)
>  File "/opt/software/mailman/Mailman/Handlers/Scrubber.py", line 408, 
>in process
>replace_payload_by_text(msg, sep.join(text), charset)
>  File "/opt/software/mailman/Mailman/Handlers/Scrubber.py", line 170, 
>in replace_payload_by_text
>msg.set_payload(text, charset)
>  File "/usr/lib64/python2.4/email/Message.py", line 218, in
set_payload
>self.set_charset(charset)
>  File "/usr/lib64/python2.4/email/Message.py", line 242, in
set_charset
>raise TypeError(charset)
>TypeError: us-ascii


This is a problem in the 2.1.12rc1 release. See the post at
<http://mail.python.org/pipermail/mailman-announce/2009-January/000129.h
tml>
for the fix. There are a couple of other problems too. I will be
releasing 2.1.12rc2 in a day or so.


[...]
>snipet from smtp-failure:
>.org>
>Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@lists.tigr.org 
>failed with code -1: (111, 'Connection refused') Feb 04 17:27:18 2009 
>(4766) Low level smtp error: (111, 'Connection refused'), msgid: 
><20090204222702.7f98420...@lists.jcvi.org>
>Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@lists.tigr.org 
>failed with code -1: (111, 'Connection refused') Feb 04 17:27:18 2009 
>(4766) Low level smtp error: (111, 'Connection refused'), msgid: 
><20090204222701.70f4f20...@lists.jcvi.org>
>Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@lists.tigr.org 
>failed with code -1: (111, 'Connection refused') Feb 04 17:27:18 2009 
>(4766) Low level smtp error: (111, 'Connection refused'), msgid: 
><20090204222702.9d7d820...@lists.jcvi.org>
>Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@lists.tigr.org 
>failed with code -1: (111, 'Connection refused')


Your MTA is not accepting connects from Mailman, at least part of the
time. See the FAQ at <http://wiki.list.org/x/-IA9> for debugging hints
if this is an ongoing problem.

>
>What's in Mailman's qfiles/in/ directory?
>empty
>
>What are the other two high cpu runners (pids 4951 and 4946)?
>Yes that's it.


Yes, but which runners are they?

ps -fwp 4946 4951



>Does Mailman work normally except for this high cpu usage?
>
>First after moving my lists server all basic functions work, however 
>the list server is not archiving, even when I select daily.


The not archiving is the issue referred to above. Once you apply the
patch from
<http://mail.python.org/pipermail/mailman-announce/2009-January/000129.h
tml>,
you can check that you have no 'old' files in qfiles/shunt and run
bin/unshunt to archive the the messages that were shunted during
archiving.


>This

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

2009-02-06 Thread Goodman, William

What release did you upgrade from?
>From 2.1.7 to 2.1.12rc1

What's in Mailman's logs?
snipet from bounce:
Feb 05 13:48:17 2009 (4760) gme_conference: bounce message w/no
discernable addresses:
<200902051848.n15imfx1011...@independence.tigr.org>
Feb 05 13:48:17 2009 (4760) gme_conference: forwarding unrecognized,
message-id: <200902051848.n15imfx1011...@independence.tigr.org>
snipet from error:
Feb 04 19:13:23 2009 (4759) Traceback (most recent call last):
  File "/opt/software/mailman/Mailman/Queue/Runner.py", line 120, in
_oneloop
self._onefile(msg, msgdata)
  File "/opt/software/mailman/Mailman/Queue/Runner.py", line 191, in
_onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File "/opt/software/mailman/Mailman/Queue/ArchRunner.py", line 73, in
_dispose
mlist.ArchiveMail(msg)
  File "/opt/software/mailman/Mailman/Archiver/Archiver.py", line 216,
in ArchiveMail
h.processUnixMailbox(f)
  File "/opt/software/mailman/Mailman/Archiver/pipermail.py", line 564,
in processUnixMailbox
m = mbox.next()
  File "/usr/lib64/python2.4/mailbox.py", line 35, in next
return self.factory(_Subfile(self.fp, start, stop))
  File "/opt/software/mailman/Mailman/Mailbox.py", line 89, in scrubber
return mailbox.scrub(msg)
  File "/opt/software/mailman/Mailman/Mailbox.py", line 109, in scrub
return self._scrubber(self._mlist, msg)
  File "/opt/software/mailman/Mailman/Handlers/Scrubber.py", line 408,
in process
replace_payload_by_text(msg, sep.join(text), charset)
  File "/opt/software/mailman/Mailman/Handlers/Scrubber.py", line 170,
in replace_payload_by_text
msg.set_payload(text, charset)
  File "/usr/lib64/python2.4/email/Message.py", line 218, in set_payload
self.set_charset(charset)
  File "/usr/lib64/python2.4/email/Message.py", line 242, in set_charset
raise TypeError(charset)
TypeError: us-ascii
snipet from qrunner:
(pid: 4948, sig: None, sts: 15, class: CommandRunner, slice: 1/1)
Feb 04 17:25:24 2009 (4759) ArchRunner qrunner started.
Feb 04 17:25:24 2009 (4762) CommandRunner qrunner started.
Feb 04 17:25:24 2009 (4760) BounceRunner qrunner started.
Feb 04 17:25:24 2009 (4765) NewsRunner qrunner started.
Feb 04 17:25:24 2009 (4764) IncomingRunner qrunner started.
Feb 04 17:25:24 2009 (4767) VirginRunner qrunner started.
Feb 04 17:25:24 2009 (4766) OutgoingRunner qrunner started.
Feb 04 17:25:24 2009 (4768) RetryRunner qrunner started.
snipet from smtp-failure:
.org>
Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@lists.tigr.org
failed with code -1: (111, 'Connection refused')
Feb 04 17:27:18 2009 (4766) Low level smtp error: (111, 'Connection
refused'), msgid: <20090204222702.7f98420...@lists.jcvi.org>
Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@lists.tigr.org
failed with code -1: (111, 'Connection refused')
Feb 04 17:27:18 2009 (4766) Low level smtp error: (111, 'Connection
refused'), msgid: <20090204222701.70f4f20...@lists.jcvi.org>
Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@lists.tigr.org
failed with code -1: (111, 'Connection refused')
Feb 04 17:27:18 2009 (4766) Low level smtp error: (111, 'Connection
refused'), msgid: <20090204222702.9d7d820...@lists.jcvi.org>
Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@lists.tigr.org
failed with code -1: (111, 'Connection refused')

The other logs show normal logging nor errors or warnings

What's in Mailman's qfiles/in/ directory?
empty

What are the other two high cpu runners (pids 4951 and 4946)?
Yes that's it.

Does Mailman work normally except for this high cpu usage?

First after moving my lists server all basic functions work, however the
list server is not archiving, even when I select daily.
This is most likely because users cannot reply because they get bounced
with:
 
Your message did not reach some or all of the intended recipients.
Subject: RE: [Mylist] Test message
Sent: 2/4/2009 6:12 PM
The following recipient(s) could not be reached:

myl...@jcvi.org on 2/4/2009 6:12 PM

The e-mail account does not exist at the organization this message was
sent to. Check the e-mail address, or contact the recipient directly to
find out the correct address.




-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net] 
Sent: Thursday, February 05, 2009 2:14 PM
To: Goodman, William; mailman-users@python.org
Subject: Re: [Mailman-Users] mailman python-2.4 using 96% cpu

Goodman, William wrote:
> 
>After downloading and installing the latest version of 
>mailman-2.1.12rc1 and I'm using Apache-2.2-11 and 
>Postfix-2.3.3-2.1.el5_2. On CentOS 5.2 (RedhHat) for some reason I 
>can't understand the CPU usage is at 96% for mailman. When I do a top I

>get:
> 
>top - 11:18:13 up 16:38,  1 user,  load aver

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

2009-02-05 Thread Mark Sapiro

Goodman, William wrote:
>
>Theses are the high cpu grabbers:
>
>mailman   4764  4751 74 Feb04 ?17:00:03 /usr/bin/python2.4
>/opt/software/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
>
>UIDPID  PPID  C STIME TTY  TIME CMD
>mailman   4766  4751 22 Feb04 ?05:08:33 /usr/bin/python2.4
>/opt/software/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
>
>UIDPID  PPID  C STIME TTY  TIME CMD
>mailman   4760  4751  4 Feb04 ?01:01:34 /usr/bin/python2.4
>/opt/software/mailman/bin/qrunner --runner=BounceRunner:0:1 -s 


OK, thanks.


>Also there's a dead like to the patch location you sent me.


Are you trying to go the URL I sent or are you trying to go to the
first of the two lines your MUA split it into?

>tml>,

In any case, here is the patch:

=== modified file 'Mailman/Handlers/Scrubber.py'
--- Mailman/Handlers/Scrubber.py2008-12-01 04:30:43 +
+++ Mailman/Handlers/Scrubber.py2009-01-12 17:45:14 +
@@ -1,4 +1,4 @@
-# Copyright (C) 2001-2008 by the Free Software Foundation, Inc.
+# Copyright (C) 2001-2009 by the Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or
 # modify it under the terms of the GNU General Public License
@@ -167,6 +167,9 @@
 # message by a text (scrubbing).
 del msg['content-type']
 del msg['content-transfer-encoding']
+if isinstance(charset, unicode):
+# email 3.0.1 (python 2.4) doesn't like unicode
+charset = charset.encode('us-ascii')
 msg.set_payload(text, charset)

This patch can also be found at


Two other patches you may want to apply are at

and
,
but as I said I will be releasing 2.1.12rc2 in a day or two with these
changes.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

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

2009-02-05 Thread Mark Sapiro

Mark Sapiro wrote:
>
>The not archiving is the issue referred to above. Once you apply the
>patch from
>,
>you can check that you have no 'old' files in qfiles/shunt and run
>bin/unshunt to archive the the messages that were shunted during
>archiving.


Note that you will need to restart Mailman after applying the patch and
before running bin/unshunt.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

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

2009-02-05 Thread Mark Sapiro

Goodman, William wrote:

>What release did you upgrade from?
>>From 2.1.7 to 2.1.12rc1


OK


>What's in Mailman's logs?
[...]
>snipet from error:
>Feb 04 19:13:23 2009 (4759) Traceback (most recent call last):
>  File "/opt/software/mailman/Mailman/Queue/Runner.py", line 120, in
>_oneloop
>self._onefile(msg, msgdata)
>  File "/opt/software/mailman/Mailman/Queue/Runner.py", line 191, in
>_onefile
>keepqueued = self._dispose(mlist, msg, msgdata)
>  File "/opt/software/mailman/Mailman/Queue/ArchRunner.py", line 73, in
>_dispose
>mlist.ArchiveMail(msg)
>  File "/opt/software/mailman/Mailman/Archiver/Archiver.py", line 216,
>in ArchiveMail
>h.processUnixMailbox(f)
>  File "/opt/software/mailman/Mailman/Archiver/pipermail.py", line 564,
>in processUnixMailbox
>m = mbox.next()
>  File "/usr/lib64/python2.4/mailbox.py", line 35, in next
>return self.factory(_Subfile(self.fp, start, stop))
>  File "/opt/software/mailman/Mailman/Mailbox.py", line 89, in scrubber
>return mailbox.scrub(msg)
>  File "/opt/software/mailman/Mailman/Mailbox.py", line 109, in scrub
>return self._scrubber(self._mlist, msg)
>  File "/opt/software/mailman/Mailman/Handlers/Scrubber.py", line 408,
>in process
>replace_payload_by_text(msg, sep.join(text), charset)
>  File "/opt/software/mailman/Mailman/Handlers/Scrubber.py", line 170,
>in replace_payload_by_text
>msg.set_payload(text, charset)
>  File "/usr/lib64/python2.4/email/Message.py", line 218, in set_payload
>self.set_charset(charset)
>  File "/usr/lib64/python2.4/email/Message.py", line 242, in set_charset
>raise TypeError(charset)
>TypeError: us-ascii


This is a problem in the 2.1.12rc1 release. See the post at

for the fix. There are a couple of other problems too. I will be
releasing 2.1.12rc2 in a day or so.


[...]
>snipet from smtp-failure:
>.org>
>Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@lists.tigr.org
>failed with code -1: (111, 'Connection refused')
>Feb 04 17:27:18 2009 (4766) Low level smtp error: (111, 'Connection
>refused'), msgid: <20090204222702.7f98420...@lists.jcvi.org>
>Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@lists.tigr.org
>failed with code -1: (111, 'Connection refused')
>Feb 04 17:27:18 2009 (4766) Low level smtp error: (111, 'Connection
>refused'), msgid: <20090204222701.70f4f20...@lists.jcvi.org>
>Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@lists.tigr.org
>failed with code -1: (111, 'Connection refused')
>Feb 04 17:27:18 2009 (4766) Low level smtp error: (111, 'Connection
>refused'), msgid: <20090204222702.9d7d820...@lists.jcvi.org>
>Feb 04 17:27:18 2009 (4766) delivery to mailman-ow...@lists.tigr.org
>failed with code -1: (111, 'Connection refused')


Your MTA is not accepting connects from Mailman, at least part of the
time. See the FAQ at  for debugging hints
if this is an ongoing problem.

>
>What's in Mailman's qfiles/in/ directory?
>empty
>
>What are the other two high cpu runners (pids 4951 and 4946)?
>Yes that's it.


Yes, but which runners are they?

ps -fwp 4946 4951



>Does Mailman work normally except for this high cpu usage?
>
>First after moving my lists server all basic functions work, however the
>list server is not archiving, even when I select daily.


The not archiving is the issue referred to above. Once you apply the
patch from
,
you can check that you have no 'old' files in qfiles/shunt and run
bin/unshunt to archive the the messages that were shunted during
archiving.


>This is most likely because users cannot reply because they get bounced
>with:
> 
>Your message did not reach some or all of the intended recipients.
>Subject: RE: [Mylist] Test message
>Sent: 2/4/2009 6:12 PM
>The following recipient(s) could not be reached:
>
>myl...@jcvi.org on 2/4/2009 6:12 PM
>
>The e-mail account does not exist at the organization this message was
>sent to. Check the e-mail address, or contact the recipient directly to
>find out the correct address.
>
>


This is an MTA issue. Were these list's working before the upgrade?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

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

2009-02-05 Thread Mark Sapiro

Goodman, William wrote:
> 
>After downloading and installing the latest version of mailman-2.1.12rc1
>and I'm using Apache-2.2-11 and
>Postfix-2.3.3-2.1.el5_2. On CentOS 5.2 (RedhHat) for some reason I can't
>understand the CPU usage is
>at 96% for mailman. When I do a top I get:
> 
>top - 11:18:13 up 16:38,  1 user,  load average: 2.78, 2.76, 2.62
>Tasks: 122 total,   2 running, 120 sleeping,   0 stopped,   0 zombie
>Cpu(s): 33.4%us,  2.3%sy,  0.0%ni, 64.0%id,  0.2%wa,  0.0%hi,  0.1%si,
>0.0%st
>Mem:   3866536k total,  2471544k used,  1394992k free,   409096k buffers
>Swap:  4194296k total,0k used,  4194296k free,  1435408k cached
> 
>PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
>
>4949 mailman   25   0  175m  37m 2760 R   97  1.0 944:03.94 python2.4
>
>4951 mailman   16   0  168m  30m 2828 S   12  0.8 288:29.09 python2.4
>
>4946 mailman   16   0  171m  33m 2752 S2  0.9  57:05.67 python2.4
>
>11093 postfix   15   0 54512 2848 2228 S1  0.1   0:00.29 smtpd
>
>14 root  10  -5 000 S0  0.0   1:02.48 events/0
>
>3935 root  10  -5 000 S0  0.0   2:42.83 kjournald
>
>6479 root  15   0 88068 3232 2516 S0  0.1   0:00.17 sshd
>
>10942 postfix   15   0 54212 2624 2064 S0  0.1   0:00.20 local
>
>11157 postfix   15   0 54252 2360 1820 S0  0.1   0:00.11 cleanup
>
>11172 postfix   16   0 55140 2356 1820 S0  0.1   0:00.10 cleanup
>
> 
>When I search for that PID I get this:
> 
># ps -ef | grep 4949
>mailman   4949  4938 94 Feb03 ?15:44:50 /usr/bin/python2.4
>/opt/software/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s


What release did you upgrade from?

What's in Mailman's logs?

What's in Mailman's qfiles/in/ directory?

What are the other two high cpu runners (pids 4951 and 4946)?

Does Mailman work normally except for this high cpu usage?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

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

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

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

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

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

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

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

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

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

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

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

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

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

13 matches

Site Navigation

Mail list logo

Footer information