Thanks, Barry and Mark, I'm resigned to my fate.
Just as additional info on the circumstances:
- The system crash seems to have been caused by disk errors on an alleged
RAID array (still working on that problem), so that may account for the file
corruption.
- We were running Mailman 2.1, so the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 8, 2007, at 6:36 PM, Mark Sapiro wrote:
> Normally, if the config.pck is corrupt, we should fall back to the
> config.pck.last which should be OK. It is difficult to see how the
> logic could result in both files being corrupt, but strange thin
Ken Crater wrote:
>
>Attempting to access our more important email list via the web interface
>results in the following traceback:
>
>Traceback (most recent call last):
> File "/var/mailman/scripts/driver", line 87, in run_main
>main()
> File "/var/mailman/Mailman/Cgi/admin.py", line 70, in m
Hi all,
We're using Mailman 2.1 (in fact, our control.com site was the impetus for
v. 2.1) and appear to have suffered a severe problem in connection with a
system crash over the weekend.
Attempting to access our more important email list via the web interface
results in the following traceback:
