Re: [Mailman-Developers] .nfs* lock files
[Melissa G. Ng]
I think it may be related to a problem I have regarding the cgi script "listinfo".
I don't think so.
When I try to invoke "<mailman-server>/mailman/listinfo" I get
[...]
File "/user/mailman/Mailman/MailList.py", line 812, in Load dict = marshal.load(file) MemoryError:
[...]
But when I invoke the individual lists's "listinfo" page, it comes back fine.
I think one of your lists have had its config.db corrupted (but I don't know _why_ that has happened). If so, you can discover which list is causing you grief like this:
$ whoami mailman $ cd $ python Python 1.5.2 (#6, Dec 1 1999, 20:04:16) [C] on sunos5 Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
from Mailman import Utils, MailList for name in Utils.list_names(): ... print "About to attempt load of list", name ... mlist = MailList.MailList(name, lock=0) ... About to attempt load of list list1 [...] About to attempt load of list corrupt-list Traceback (innermost last):
... indicating that the corrupted list is called "corrupt-list". As the test aborts once a corrupt list is found, make sure you re-run the test until it finishes without producing any tracebacks.
Could someone please help me out with this problem?
This isn't really on topic for this list -- the correct list for such problems is mailman-users.
Cheap shot at making this post on-topic: Should there be a cron script (possibly cron/checkdbs will do) to warn the site admin about lists that have been corrupted?
Harald
"HM" == Harald Meland <Harald.Meland@usit.uio.no> writes:
HM> Cheap shot at making this post on-topic: Should there be a
HM> cron script (possibly cron/checkdbs will do) to warn the site
HM> admin about lists that have been corrupted?I could probably elaborate on the mechanism in MailList.Load() -- see the CVS tree -- where if config.db is missing, it'll fallback to config.db.last. If it falls back, then it shutil.copy()'s config.db.last to config.db so the logic in Save() doesn't need to be changed.
We could probably do the same thing if the unmarshalling of config.db fails. But why you'd get a MemoryError is beyond me, unless the corruption tickles a bug in Python.
-Barry
participants (2)
-
bwarsaw＠python.org -
Harald Meland