sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] NOT AGAIN


From: Dan Egli
Subject: Re: [Sks-devel] NOT AGAIN
Date: Mon, 28 Jun 2004 14:18:24 -0600
User-agent: Mozilla Thunderbird 0.6 (Windows/20040502)

Chris Kuethe wrote:

OK, what happens if you move the logs out of the way, remove the __db.*
files, and try recovery again?

something sounds very very wrong... almost like ocaml/db are getting
getting confused over which version of headers or library to use. ick

CK

On Mon, 28 Jun 2004, Dan Egli wrote:

Dan Egli wrote:

Chris Kuethe wrote:

cd /home/sks/KDB
db4_recover
db4_archive | xargs rm
cd /home/sks/PTree
db4_recover
db4_archive | xargs rm
cd ..
/home/sks/bin/sks cleandb
/home/sks/bin/sks db &
/home/sks/bin/sks recon &



No good.

address@hidden KDB]$ db_recover
db_recover: Program version 4.2 doesn't match environment version
db_recover: Ignoring log file: log.0000000055: unreadable log version 7
db_recover: Ignoring log file: log.0000000055: unreadable log version 7
db_recover: Ignoring log file: log.0000000055: unreadable log version 7
db_recover: Ignoring log file: log.0000000054: unreadable log version 7
db_recover: Ignoring log file: log.0000000053: unreadable log version 7
db_recover: Ignoring log file: log.0000000052: unreadable log version 7
db_recover: Ignoring log file: log.0000000051: unreadable log version 7
db_recover: Ignoring log file: log.0000000050: unreadable log version 7
address@hidden KDB]$ /usr/local/BerkeleyDB.4.2/bin/db_recover
db_recover: Ignoring log file: log.0000000055: unreadable log version 7
db_recover: Ignoring log file: log.0000000055: unreadable log version 7
db_recover: Ignoring log file: log.0000000055: unreadable log version 7
db_recover: Ignoring log file: log.0000000054: unreadable log version 7
db_recover: Ignoring log file: log.0000000053: unreadable log version 7
db_recover: Ignoring log file: log.0000000052: unreadable log version 7
db_recover: Ignoring log file: log.0000000051: unreadable log version 7
db_recover: Ignoring log file: log.0000000050: unreadable log version 7


the first is the system DB (4.2.52-3.1)
the 2nd is a generic db_recover compiled from sources.

Same type of thing happens when I try to run db_archive:
db_archive: Ignoring log file: log.0000000055: unreadable log version 7

that's why I needed to guess on the log files to rm.




FWIW, the same happens if I try to use the compat-db programs, only worse:

address@hidden KDB]$ db41_recover
db_recover: unable to join the environment
db_recover: Ignoring log file: log.0000000056: unsupported log version 8
db_recover: Invalid log file: log.0000000056: Invalid argument
db_recover: PANIC: Invalid argument
db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: fatal region error detected; run recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery


I really hate the berkeley utils. Isn't this like a chicken and the egg problem? "Run database recovery", and error reported WHILE TRYING TO RUN A DATABASE RECOVERY. You've got to be kidding me.


I have to leave in an hour. I hope someone can help me recover the DB before then else I'll just have to rebuild it I guess. That will take all day.


--
-- Dan


_______________________________________________
Sks-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/sks-devel



They are getting confused. I think I may just rm the database and then rm the compat programs since I don't use them anyway. Long and ugly but it might fix it. I tried rm'ing the last log and was able to use the compat recover programs ok, but when I run cleandb it croaks:

Fatal error: exception Bdb.DBError("DB_ENV->log_flush: LSN of 55/4776811 past current end-of-log of 1/881")

I also want to scream at RedHat for putting the COMPAT db libs in the default install set. NOT a good idea I feel.


--
-- Dan




reply via email to

[Prev in Thread] Current Thread [Next in Thread]