Re: SimpleDB errors after Debian 3.0->3.1 upgrade

Brent Chapman <[email protected]>
Newsgroups gmane.mail.majordomo.majordomo2.devel
Message-ID <p0623091bc0c88ffc512f@[64.142.69.207]>
At 11:52 AM -0500 6/28/06, Jason L Tibbitts III wrote:
>  >>>>> "BC" == Brent Chapman <[email protected]> writes:
>
>BC> I upgraded from Debian 3.0 (Woody) to Debian 3.1 (Sarge) last
>BC> night. Since the upgrade, pretty much anything I attempt to do
>BC> with Majordomo2 yields many instances of the following warning
>BC> (though the commands seem to work):
>
>Incompatible DB version upgrade?  You can't in general just upgrade
>the DB library and have old files work; there's usually a db_upgrade
>utility that handles the necessary changes.
>
>  - J<

Yeah, that was it.  Jeez, what a pain in the butt...  First I had to 
figure out what version of libdb the new Perl was using; it looked 
like libdb4.2, according to the dependencies.  OK, where are the db_* 
utilities for libdb4.2?  Hmm, there don't seem to be any Debian 
packages for that, but there's a libdb3-util package which contains 
db3_update and related programs; I wonder if that'll work?  Well, one 
way to find out is to back everything up and give it a try...  Yup, 
that solves the warnings from MJ2; however, the db3_verify program 
gripes about warnings and errors with quite a few of the files... 
OK, use "db3_dump -r" to dump a recovery version of each .D that it's 
complaining about, move the originals aside, and use db3_load to 
create a new one from the dump...  Yup, that seems to have worked, so 
far...

So much for going to the gym this morning.

Anyway, thanks for the clue that got me headed in the right direction!

-Brent
-- 
Brent Chapman <[email protected]> -- Great Circle Associates, Inc.
Specializing in network infrastructure for Silicon Valley since 1989
For info about us and our services, please see http://www.greatcircle.com/
Great Circle Waypoints Blog: http://www.greatcircle.com/blog
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.