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

[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
<http://mail.python.org/pipermail/mailman-announce/2009-January/000129.html>
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-owner at 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.7F98420066 at lists.jcvi.org>
>Feb 04 17:27:18 2009 (4766) delivery to mailman-owner at 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.70F4F20070 at lists.jcvi.org>
>Feb 04 17:27:18 2009 (4766) delivery to mailman-owner at 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.9D7D82006D at lists.jcvi.org>
>Feb 04 17:27:18 2009 (4766) delivery to mailman-owner at 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.html>,
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:
>
>mylist at 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.
>
><EXCHANGE.XXXX.ORG #5.1.1>


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

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan