[Mailman-Users] Looking for Help recovering from Disk Full

Mark Sapiro mark at msapiro.net
Wed May 5 16:06:16 CEST 2010

David Devereaux-Weber wrote:

>I'm running Mailman version 2.1.9 on Solaris.  I had a disk full
>situation.  I'm resolving problems as I encounter them.  Can anyone
>shed some light on this error message?  Is it possible to delete the
>held messages file to clear this up?
>Your "cron" job on ddwsvcs
>/usr/local/bin/python -S /usr/local/mailman/cron/checkdbs
>produced the following output:
>Traceback (most recent call last):
>  File "/usr/local/mailman/cron/checkdbs", line 203, in ?
>    main()
>  File "/usr/local/mailman/cron/checkdbs", line 104, in main
>    discarded = auto_discard(mlist)
>  File "/usr/local/mailman/cron/checkdbs", line 192, in auto_discard
>    heldmsgs = mlist.GetHeldMessageIds()
>  File "/usr/local/mailman/Mailman/ListAdmin.py", line 143, in GetHeldMessageIds
>    return self.__getmsgids(HELDMSG)
>  File "/usr/local/mailman/Mailman/ListAdmin.py", line 138, in __getmsgids
>    ids = [k for k, (op, data) in self.__db.items() if op == rtype]
>TypeError: unpack non-sequence

Some list's lists/LISTNAME/request.pck file is corrupt. Yes, it can be
deleted if you know which one. If you don't, you can try

cd ~mailman       (or whatever)
for list in `bin/list_lists --bare`; do
echo $list
bin/dumpdb lists/$list/request.pck > /dev/null

which should throw the same TypeError on the bad file.

Note that this will lose everything that you would have seen on the
list's admindb page were the file not corrupted, but it's basically
lost anyway. If there are held messages, they are in files named
data/heldmsg-LISTNAME-nnn.*. If you want to try to recover these (if
any), see <http://www.msapiro.net/scripts/hold_again>.

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

More information about the Mailman-Users mailing list