Charlie Clark wrote: > >we have a problem with just one of our mailing lists. Unfortunately I >do not have direct access to the Mailman install.
Then you won't be able to fix this. You'll need to get whoever does have access to do it. >There are lots of errors of the form: > >Oct 16 21:45:01 2008 (2881) SHUNTING: >1224186301.857964+44d57ae24346f2e593571310b2fb5a9262fdf059 >Oct 16 21:50:03 2008 (2881) Uncaught runner exception: bad marshal data >Oct 16 21:50:03 2008 (2881) Traceback (most recent call last): >File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop > self._onefile(msg, msgdata) >File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, 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/Moderate.py", line 109, in >process > Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost) >File "/usr/local/mailman/Mailman/Handlers/Hold.py", line 207, in >hold_for_approval > id = mlist.HoldMessage(msg, reason, msgdata) >File "/usr/local/mailman/Mailman/ListAdmin.py", line 205, in HoldMessage > self.__opendb() >File "/usr/local/mailman/Mailman/ListAdmin.py", line 82, in __opendb > self.__db = marshal.load(fp) >ValueError: bad marshal data The above error says: This is Mailman 2.1.4 or older and the file lists/LISTNAME/request.db is corrupt. Simply removing the file should allow the list to resume processing, although there may be some messages that were held before the corruption occurred that won't be in the admindb interface for the list. The shunted messages can be reprocessed by running bin/unshunt, but before doing so it is always a good idea to examine the files in qfiles/shunt with bin/dumpdb or bin/show_qfiles and cull out any old ow unwanted ones. >I have access to a copy of the Mailman install but I've not been able >to work out how to check which file is defect. I can see that e-mails >are still arriving and being processed and added to the archive but >nothing is actually sent to the list. Other lists are fine. The message that produced the above traceback shouldn't be in the archive. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
