Problem reading old wallet [RESOLVED]

[teathsch]

My old wallets from an old binary won't scan with merged-mining sources.

I don't know the old binary version, but the last modified time is: Modify: 2011-05-24 00:59:00.000000000 -0700

It's not a big deal since I was able to transfer out my NMC, but it is a problem with testnet coins since I can't get them confirmed on the forked chain.

#************************
#EXCEPTION: 22DbRunRecoveryException
#DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
#bitcoin in AppInit()
#
#terminate called after throwing an instance of 'DbRunRecoveryException'
# what(): DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
#Aborted

I checked permissions and that's not it. doublec suggested that it could be a mismatched libdb, which makes sense. Then again, libdb is pretty mature, so it's hard to say.

Again, I've been able to work around it by transferring out my NMC and generating new testnet NMC, but I'm posting this per a request on IRC.

[nodemaster]

A few questions:

Could you please verify if you transfered anything on old-testnet above block 13721, which was generated on 04/08/2011 17:08:07 (http://testnet.explorer.dot-bit.org/b/13721)?

Have you tried to clean your testnet directory, removing everything except wallet.dat and have the client redownload the entire blockchain?

Thank you for bringing this up because I guess most users tested with a fresh wallet.dat but we need a flawless migration path.

[teathsch]

I was able to get my testnet coins out too.

I think that what I did before was..

1. download blockchain
2. try to rescan old wallet

When I did..

1. clean dir + old wallet
2. download blockchain

..it worked.

To answer your question: I never transferred anything past 13721 (until now when I got the wallet to load) since I knew that it wouldn't confirm.