[Mailman-Developers] Error detection
arturs at iidea.pl
Thu Jan 23 11:48:13 EST 2003
I would like to suggest enhancing error detection
routines in Mailman. Recently I have experienced a minor
file corruption, and the results were a bit frustrating.
Although the lists seemed to work fine, neither cron
jobs, command-line tool nor WWW interface would.
The cryptic message I got was always ending with:
Traceback (most recent call last):
File "./checkdbs", line 136, in ?
File "./checkdbs", line 55, in main
mlist = MailList.MailList(name)
File "/usr/lib/mailman/Mailman/MailList.py", line 99, in __init__
File "/usr/lib/mailman/Mailman/MailList.py", line 149, in Lock
File "/usr/lib/mailman/Mailman/MailList.py", line 573, in Load
dict, e = self.__load(file)
File "/usr/lib/mailman/Mailman/MailList.py", line 546, in __load
dict = loadfunc(fp)
cPickle.UnpicklingError: unpickling stack underflow
It took a while to find out where I should look for the
error. I examined the value of fp, then checked out
databases in list directories and found out one of
config.pck's was corrupted. I overwrote it
with config.pck.last and everything started to
work fine. Maybe something could be done to
give the user the cause of thje error in a more explicit
way? I thought Mailman should open config.pck.last
automatically if config.pck is corrupted.
More information about the Mailman-Developers