[Mailman-Users] Mailman Using 70- 90% of CPU

NOW Website Coordinator webperson at now.org
Fri May 2 19:50:58 CEST 2003


It looks like someone else is having the same problem:

>·       From: Ray Dzek
>·       Subject: [Mailman-Users] Python 100% CPU
>·       Date: Sun, 30 Mar 2003 08:36:13 -0800
>
>Okay ...
>
>Mailman 2.1.1
>Python  2.2.1-17
>Postfix 1.1.11-5
>
>I finally appear to have the right combination of --with-mail-gid
>and --with-cgi-gid.  I am not getting those errors anymore.  I had several
>other "issues" because I am running dual instances of Postfix and had a
>hostname circular reference problem that also needed to get fixed (total
>n00b action on my part).
>
>So...  Now when I send an email to my test list, python grabs all the CPU
>and just hangs there until I kill the process.  There are only 3 addresses
>in the list.  mailmanctl and qrunner are both in the process list.  There
>are no log entries with a time stamp with when I sent the test mail accept
>this in /mailman/logs/qrunner:
>
>Mar 29 16:52:03 2003 (1010) OutgoingRunner qrunner caught SIGTERM.
>Stopping.
>Mar 29 16:52:03 2003 (1010) OutgoingRunner qrunner exiting.
>Mar 29 16:52:03 2003 (5227) Master qrunner detected subprocess exit
>(pid: 1010, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1)
>
>Any ideas?   Thanks in advance.
>
>Ray



Also when I stop mailman with mailmanctl stop, I get the following in the 
qrunner log, with only Outgoing having a different message (about the 
SIGTERM -- have no idea if this means anything):
May 02 13:43:32 2003 (22561) Master qrunner detected subprocess exit
(pid: 22566, sig: None, sts: 15, class: NewsRunner, slice: 1/1)
May 02 13:43:32 2003 (22561) Master qrunner detected subprocess exit
(pid: 22564, sig: None, sts: 15, class: CommandRunner, slice: 1/1)
May 02 13:43:32 2003 (22561) Master qrunner detected subprocess exit
(pid: 22568, sig: None, sts: 15, class: VirginRunner, slice: 1/1)
May 02 13:43:32 2003 (22567) OutgoingRunner qrunner caught SIGTERM.  Stopping.
May 02 13:43:32 2003 (22567) OutgoingRunner qrunner exiting.
May 02 13:43:32 2003 (22561) Master qrunner detected subprocess exit
(pid: 22567, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1)


In answer to Will Yardley's question to my previous message:
>What happens if you kill those processes? What about if you stop, and
>restart mailman (via mailmanctl)?
>You could also try "strace -p[pid]" and see if you can see what (if
>anything) the process is doing.
>Usually, when I see really long running mailman procs like that eating
>up so much CPU, I kill them.

As soon as I restart Mailman, it uses up around 70-90% of my CPU with the 
outgoing Runner job.  It's not one run away job, I can recreate it in less 
than a minute.  And we haven't sent out any messages today, mailman has 
just sent some sub/unsub notices out.

I had this problem as I said on our old machine, I just figured it was 
underpowered.  But the problem hasn't gone away with a much faster machine, 
different OS, different web server.


Sarah Stapleton-Gray
--------------------------------------------
Web Site Coordinator
National Organization for Women
http://www.now.org






More information about the Mailman-Users mailing list