[Mailman-Developers] re: Much cpu/memory load

Danny Terweij danny@terweij.nl
Thu Oct 31 20:41:52 2002


From: "Andrew D. Clark" <andrew.clark@ucsb.edu>

> I've had the same problem.  ArchRunner seems to have serious performance
> problems if you've got heavy list activity and are archiving to both
> pipermail and mbox.  I "fixed" it by setting ARCHIVE_TO_MBOX=1.  This will
> only archive to mbox, so your pipermail archives won't be updated.  You
> should be able to generate pipermail archives by hand later with bin/arch
> list_name.  It isn't an ideal solution, but at least your message will
move
> out of the archive queue.


Hmmzz. i am now trying to reboot my machine with

 9:33pm  up 1 day,  6:38,  7 users,  load average: 42.95, 41.97, 40.85

This is very bad! and this is happened after upgrade to b4(+)



> > Date: Thu, 31 Oct 2002 15:48:08 +0100
> > From: "Danny Terweij" <danny@terweij.nl>
> > To: <mailman-developers@python.org>
> > Subject: [Mailman-Developers] Much cpu/memory load
> > Message-ID: <01ab01c280ec$8739bb20$1e00a8c0@onsnet.org>
> > Content-Type: text/plain;
> > charset="iso-8859-1"
> > MIME-Version: 1.0
> > Content-Transfer-Encoding: 7bit
> > Precedence: list
> > Message: 1
> >
> > Hi,
> >
> > Because my /qfiles/archive/*.* files are not processed by the
> > qrunner/ArchRunner my linux box gets overloaded.
> > I have now 55mb unproccessed archive files at the qfiles dir.
> > The pipermail archives are not updated.
> >
> > When i do a mailmanctl stop then the Archrunner is still active. I did a
> > kill -9 PID and it stops.
> > Then i must remove all the lock files found where lockfiles are.
> >
> > Then the cpu load is back to normal.
> >
> > 24290 ?        S      0:00 /usr/bin/python2 ./mailmanctl start
> > 24291 ?        D     34:56 qrunner
> > /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
> > 24292 ?        S      0:16 qrunner
> > /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
> > 24293 ?        S      0:03 qrunner
> > /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
> > 24294 ?        S      0:31 qrunner
> > /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
> > 24295 ?        S      0:03 qrunner
> > /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
> > 24296 ?        S      0:29 qrunner
> > /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
> > 24297 ?        S      0:07 qrunner
> > /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
> >
> > I think that realy somthing is wrong with the ArchRunner. Looks like it
is
> > in a loop or is doing nothing.
> > The /qfiles/archive/ dir is growing and growing, i must stop mailman
very
> > often now otherwise de box gets overloaded.
> >
> > The load was this morning on a average of 10 and all my memory was used
> > (20mb left on swap).
> > No error and messages at the logs dir :(
> >
> > Please take a look Barry :) it is the latest cvs.
> > You may also take al look on my box if you want and have time...
> >
> > Danny Terweij
>
>
>
>
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers@python.org
> http://mail.python.org/mailman/listinfo/mailman-developers