[Mailman-Users] Mailman no longer working or working very slowly

[Mark Sapiro]

Steven Jones wrote:
>
>What's at the start of that traceback leading up to the first call to
>deepcopy?
>
>=========
>Feb 16 15:05:45 2010 (2632) Traceback (most recent call last):
>  File "/var/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
>    self._onefile(msg, msgdata)
>  File "/var/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
>    keepqueued = self._dispose(mlist, msg, msgdata)
>  File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
>    more = self._dopipeline(mlist, msg, msgdata, pipeline)
>  File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
>    sys.modules[modname].process(mlist, msg, msgdata)
>  File "/var/mailman/Mailman/Handlers/ToDigest.py", line 91, in process
>    send_digests(mlist, mboxfp)
>  File "/var/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests
>    send_i18n_digests(mlist, mboxfp)
>  File "/var/mailman/Mailman/Handlers/ToDigest.py", line 297, in send_i18n_digests
>    mimedigest.attach(MIMEMessage(copy.deepcopy(msg)))
>  File "/usr/lib64/python2.2/copy.py", line 186, in deepcopy
>    y = copierfunction(x, memo)
>  File "/usr/lib64/python2.2/copy.py", line 283, in _deepcopy_inst
>    state = deepcopy(state, memo)
>  File "/usr/lib64/python2.2/copy.py", line 186, in deepcopy
>    y = copierfunction(x, memo)
>  File "/usr/lib64/python2.2/copy.py", line 246, in _deepcopy_dict
>    y[deepcopy(key, memo)] = deepcopy(x[key], memo)
>=========


There is a hosed message (some kind of invalid MIME structure that
parses into an email.message object with a circular reference) in the
lists/LISTNAME/digest.mbox file for some list.

You should be able to determine what list by running bin/dumpdb or
bin/show_qfiles against one of the files in qfiles/shunt/, e.g.
/var/mailman/qfiles/shunt/1266281245.229378+bd3f1d42e27ad38cf532b809460a0b0a8aef00e7.pck

(note your qfiles are in /var/mailman/qfiles/* - I missed that earlier)

Anyway, dumping the shunted message will hopfully tell you to what list
it was sent.

Move that list's digest.mbox aside, and the immediate problem will be
solved. I'll see if I can work up something to identify the bad
message.

Note that the messages being shunted are not the bad ones. They are all
being shunted because of the problem with some older message in the
digest.mbox.

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