[Mailman-Developers] What to do with a corrupt config.db?
Aaron D. Turner
Tue, 2 Oct 2001 14:06:40 -0700 (PDT)
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, 2 Oct 2001, J C Lawrence wrote:
> On Tue, 2 Oct 2001 11:00:14 -0700 (PDT)
> Aaron D Turner <firstname.lastname@example.org> wrote:
> > It seems all the config.db's (and their .last's) for all my lists
> > are now corrupt. At least check_db says so. Since there doesn't
> > seem to be anyway to fix this, perhaps there is a way to extract
> > the email addresses/passwords for the lists so I can recover?
> I'd be far more worried about finding out how and why. You have
> serious data corruption on your hands. Hunt that down first.
I'm guessing it has to do with the upgrade I just did. It seems to be
mailman related as these seem to be the only corrupted files on the system
that I can tell.
> config.db files are streamed python objects. If you can't load them
> under python (which you should be able to) then something is Badly
Well I know nothing about that or Python.
> About your only recourse at that point is trying to run
> strings against them.
Heh, forgot about strings. Yeah, that worked nicely. No way to recover
the passwords, but hey, at least I have my subscriber list again.
Aaron Turner <email@example.com|synfin.net|linuxkb.org> URI:www.synfin.net
They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety. -- Benjamin Franklin
pub 1024D/F86EDAE6 Sig: 3167 CCD6 6081 0FFC B749 9A8F 8707 9817 F86E DAE6
All emails by me are PGP signed; a lack of a signature indicates a forgery.
I have retired my PGP 2.6.2 key: FBE1 CEED 57E4 AB80 596E 60BF 451B 20E8
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Public key at: http://www.synfin.net/aturner/pgpkey.asc
-----END PGP SIGNATURE-----