Re: [Mailman-Developers] What to do with a corrupt config.db?
On Tue, 2 Oct 2001 14:06:40 -0700 (PDT) Aaron D Turner aturner@pobox.com wrote:
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.
If you upgraded Mailman, ensure that the upgrade process also upgraded the config.db's to the new format. There's a command in ~/bin to do that.
Heh, forgot about strings. Yeah, that worked nicely. No way to recover the passwords, but hey, at least I have my subscriber list again.
Yeah, I've been there (while tracking a nasty kernel bug that kept whacking my filesystem). Not I have cron jobs that email me the results of ~/bin/dump_config.
-- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, 2 Oct 2001, J C Lawrence wrote:
On Tue, 2 Oct 2001 14:06:40 -0700 (PDT) Aaron D Turner aturner@pobox.com wrote:
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.
If you upgraded Mailman, ensure that the upgrade process also upgraded the config.db's to the new format. There's a command in ~/bin to do that.
That's when I got the first error. Basically, I had upgraded from RH 6.2 to 7.1 which included a new version of python which wasn't compatible with the version of Mailman I was running (2.0beta5), so I upgraded mailman at which time my config.db's magically became corrupt.
Honestly, it could of been user error- it's been a while since I've done a mailman upgrade, and even though I followed the docs, I could of done something wrong. Of course, maybe there's a bug in 2.4.10/reiserfs which for some reason only effected the config.db and config.db.last. Or maybe the config.db converter doesn't like going between 2.0b5 and 2.0.6.
At this point I'm just happy all my subscriber info was restored- and the lists are far from critical in my case anyways.
Aaron Turner
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
iEYEARECAAYFAju6MNEACgkQhweYF/hu2uZu6wCeIGnQMi0F46jJz1YrQPWj6H8m JN0An2W/kGTNgkzCR7cwEUYCAj8QBsld =O38U -----END PGP SIGNATURE-----
participants (2)
-
Aaron D. Turner -
J C Lawrence