Problem reading old wallet [RESOLVED]
Posted: Sat Aug 06, 2011 8:44 am
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.
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.