[ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner

[SourceForge.net]

Bugs item #1077587, was opened at 2004-12-02 14:02
Message generated for change (Comment added) made by tkikuchi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103

Category: bounce detection
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Paul Rubin (prubin)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory Leak in Bounce Runner

Initial Comment:
Something is going bady wrong with the BouceRunner  It 
is leaking memory.  After it runs for a short time it has 
consumed hundreds of megabytes of memory.  I kill it 
with -9 and it restarts and is fine for another couple of 
hours.  Sometimes it does not restart and I have to stop 
and restart the mailman service.

This is running on a Linux box with Redhat 9 and postfix 
2.1.1 and mailman 2.1.5 and python 2.2.2

Below you will se a PS from right before I killed the 
process and below that one from a few seconds later.

If you will tell me what you need I would really like to 
get to the bottom of this, I am killing the process like 10 
times per day.  If it eats too much memory before I 
catch it then the entire system fails.

[root at tbnonline ~]# ps -U mailman  -o pid,%cpu,%
mem,stime,time,vsz,args
  PID %CPU %MEM STIME     TIME   VSZ COMMAND
12949  0.0  0.0 08:05 00:00:00  
7068 /usr/bin/python /var/mailman/bin/mailmanctl -s -q 
start
12950  0.1  0.3 08:05 00:00:02 
11176 /usr/bin/python /var/mailman/bin/qrunner --
runner=ArchRunner:0:1 -s
12951 18.9 70.8 08:05 00:08:40 
931312 /usr/bin/python /var/mailman/bin/qrunner --
runner=BounceRunner:0:1 -s
12952  0.0  0.0 08:05 00:00:00  
7040 /usr/bin/python /var/mailman/bin/qrunner --
runner=CommandRunner:0:1 -s
12953  0.0  0.1 08:05 00:00:00  
9256 /usr/bin/python /var/mailman/bin/qrunner --
runner=IncomingRunner:0:1 -s
12954  0.0  0.1 08:05 00:00:00  
7080 /usr/bin/python /var/mailman/bin/qrunner --
runner=NewsRunner:0:1 -s
12955  2.5  0.6 08:05 00:01:11 
14172 /usr/bin/python /var/mailman/bin/qrunner --
runner=OutgoingRunner:0:1 -s
12956  0.8  0.2 08:05 00:00:24 
10628 /usr/bin/python /var/mailman/bin/qrunner --
runner=VirginRunner:0:1 -s
12957  0.1  0.2 08:05 00:00:04 
13272 /usr/bin/python /var/mailman/bin/qrunner --
runner=RetryRunner:0:1 -s

[root at tbnonline ~]# ps -U mailman  -o pid,%cpu,%
mem,stime,time,vsz,args                                            
  
  PID %CPU %MEM STIME     TIME   VSZ COMMAND
12949  0.0  0.1 08:05 00:00:00  
7072 /usr/bin/python /var/mailman/bin/mailmanctl -s -q 
start
12950  0.0  0.3 08:05 00:00:02 
11176 /usr/bin/python /var/mailman/bin/qrunner --
runner=ArchRunner:0:1 -s
12952  0.0  0.0 08:05 00:00:00  
7040 /usr/bin/python /var/mailman/bin/qrunner --
runner=CommandRunner:0:1 -s
12953  0.0  0.2 08:05 00:00:00  
9256 /usr/bin/python /var/mailman/bin/qrunner --
runner=IncomingRunner:0:1 -s
12954  0.0  0.1 08:05 00:00:00  
7080 /usr/bin/python /var/mailman/bin/qrunner --
runner=NewsRunner:0:1 -s
12955  3.0  0.9 08:05 00:01:43 
13584 /usr/bin/python /var/mailman/bin/qrunner --
runner=OutgoingRunner:0:1 -s
12956  1.2  0.6 08:05 00:00:41 
10848 /usr/bin/python /var/mailman/bin/qrunner --
runner=VirginRunner:0:1 -s
12957  0.1  0.6 08:05 00:00:06 
13284 /usr/bin/python /var/mailman/bin/qrunner --
runner=RetryRunner:0:1 -s
14900 29.8  1.1 08:51 00:02:47 
13764 /usr/bin/python /var/mailman/bin/qrunner --
runner=BounceRunner:0:1 -s


----------------------------------------------------------------------

>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2004-12-17 01:29

Message:
Logged In: YES 
user_id=67709

I suggest stop automatic processing of bounces by setting
bounce_processing variable to 'No' at the admin/bounce page.
Looks like your server is very busy and unsubscribing
process due to the bounce score may interfering. 
You may also have to unsubscribe the problematic members
manually.



----------------------------------------------------------------------

Comment By: Paul Rubin (prubin)
Date: 2004-12-15 17:29

Message:
Logged In: YES 
user_id=91557

I do not have a specific number of bounces per day.  We 
send around 500,000 message per day with peak days around 
1,000,000, we know that we have some bad addresses, but 
at any given time there should not be more than 5,000 
bounce notices per day (full mailboxes are common)

As far as I can tell only certain bounce notices cause the 
leak.  We can go hours or days with memory being almost 
flat, then suddenly 200M vanishes in 2 or 3 minutes.

Is there any way I could 'hack' the code to somehow grab 
the information about what bounce notice is causing the 
problem.  Or to capture all bounce notices in some outof the 
way space that I could tar up an send to you for testing.  

If nothing else I could edit the aliases to copy all of the 
messages to a file and zip it down for you after a few days.

Does any of this make any sense?  

----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2004-12-15 00:19

Message:
Logged In: YES 
user_id=67709

My FreeBSD4.7/Solaris8 installations have no such problems.
How many bounces you get on this system?



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103