Bugs item #1656289, was opened at 2007-02-09 10:14 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1656289&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable)

Status: Pending Resolution: None Priority: 5 Private: No Submitted By: Paul Laudanski (zhenxjell) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to process the "in" folder: out of memory

Initial Comment: The files in mailman/qfiles/in are not being processed. Rather the following errors are displaying in the error log file. Its the same error over and over in version 2.1.9. Does this error effect the processing of the "in" folder? Currently 161 files are in there. The retry and out folders are empty. Feb 08 11:13:03 2007 (16016) Uncaught runner exception: out of memory Feb 08 11:13:06 2007 (16016) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SpamDetect.py", line 111, in process g.flatten(p) File "/usr/local/mailman/pythonlib/email/Generator.py", line 101, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 129, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 155, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 258, in _handle_multipart print >> self._fp, '\n--' + boundary + '--', MemoryError: out of memory Feb 08 11:13:07 2007 qrunner(16016): Traceback (most recent call last): Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 278, in ? Feb 08 11:13:07 2007 qrunner(16016): main() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 238, in main Feb 08 11:13:07 2007 qrunner(16016): qrunner.run() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 71, in run Feb 08 11:13:07 2007 qrunner(16016): filecnt = self._oneloop() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 124, in _oneloop Feb 08 11:13:07 2007 qrunner(16016): new_filebase = self._shunt.enqueue(msg, msgdata) Feb 08 11:13:08 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 106, in enqueue Feb 08 11:13:08 2007 qrunner(16016): msgsave = cPickle.dumps(_msg, protocol) Feb 08 11:13:08 2007 qrunner(16016): MemoryError : out of memory ----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro) Date: 2007-02-09 11:52

Message: Logged In: YES user_id=1123998 Originator: NO This is not a Mailman bug per se. IncomingRunner is processing a message. It calls the process() function in the SpamDetect handler which encounters the MemoryError exception which occurs when some Python process tries to allocate more memory and is denied by the OS. Normally, the offending message queue entry would be shunted and processing would continue with the next message, but the attempt to shunt the message also hits the MemoryError. I suggest first trying 'bin/mailmanctl restart' if you haven't done so in case there is a memory leak somewhere in Python. If that doesn't fix it, I think the first file in qfiles/in is probably very large and contains a very large message which is causing the problem. Try 'bin/mailmanctl stop', then move that file aside and do 'bin/mailmanctl start' and see if that resolves the issue. If it does, you may be able to examine the file with bin/dumpdb or bin/show_qfiles. If you need further help, please follow up on mailman-users@python.org. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1656289&group_id=103