[Mailman-Users] qrunner lockup / mass moderation
Stephan Uhlmann
su at su2.info
Tue May 4 02:05:53 CEST 2004
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
since a few days I have the following problem:
The qrunner locks up (strace output repeats and repeats as if the process is
caught in an endless loop) and uses 100% of my CPU.
The lock-files are dated in the future (but I have a ntp synched clock).
The only qrunner log file (which is not dated in the future) keeps saying
"Could not acquire qrunner lock".
What could be the problem?
I have two lists with a relatively large amount of messages in the moderation
queue (800+ and 1100+). Maybe the queue runner needs more and more time to
process these? The messages are all spam and can be thrown away, but I just
can't delete them by the browser admin interface. This would take too much
time. Is there another way to do such mass moderation?
I tried to move away the files in the data/ directory but then Mailman
complains about missing them, so I guess I have to do it the "Mailman way" to
keep everything consistent.
Maybe with the "withlist" tool?
In the archives I found this message:
http://mail.python.org/pipermail/mailman-users/2000-January/003419.html
but the link there points to the Mailman documentation which does not have
such a script (anymore).
I run Mailman 2.0.13 and Python 2.1.1. Yes, I know this is a pretty old setup
but I can't upgrade right now.
Cheers,
Stephan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQFAlt5h0TAeRPnvmyERAqN1AJ9Os8eTuaKPaezYGTb+BBMqEB9I0gCfaOb5
xgr+KKm4woc1yaL5a07zbfw=
=Uzhm
-----END PGP SIGNATURE-----
More information about the Mailman-Users
mailing list