Topic: Bitcoin client crashes upon decrypt (Read 2163 times)
I've confirmed the passphrase you provided me with is not correct.
Thanks for the help folks.
When I use pywallet.py with the --walletdump --password= options with my proper passphrase, pywallet.py changes from a terminal command line to the characters ">>>" and it wont take any more commands and is apparently locked up.
I am no longer receiving a DBRUNRECOVERY error. Cannot find any any error messages at all actually (even in debug.log), when the client crashes it just crashes.
Using bitcoin 0.6.2.
Thanks all
When I use pywallet.py with the --walletdump --password= options with my proper passphrase, pywallet.py changes from a terminal command line to the characters ">>>" and it wont take any more commands and is apparently locked up.
I am no longer receiving a DBRUNRECOVERY error. Cannot find any any error messages at all actually (even in debug.log), when the client crashes it just crashes.
Using bitcoin 0.6.2.
Thanks all
First of all, which bitcoin version is this?
Second, what error do you get before the crash? (look on the command-line, in debug.log, ...)
If the wallet file is corrupted at the BDB level, you can try using db4.8_dump | db4.8_load in recovery mode.
Second, what error do you get before the crash? (look on the command-line, in debug.log, ...)
If the wallet file is corrupted at the BDB level, you can try using db4.8_dump | db4.8_load in recovery mode.
This is one of the reasons the wallet file has no business being a DB!
+1
This is something that worries me greatly... I have a lot of BTC in cold storage.
However, I have tested my wallet several times prior to doing the backups.
If the wallet is unencrypted, it's pretty easy to extract the private keys from a hex editor, even if the whole thing is corrupt (assuming, of course, that the individual bytes making up the keys are themselves unharmed).
If encrypted, it's probably nearly as easy (passphrase must be known of course), but I have never dived into it to know for sure. The average wallet.dat is 99.9% fluff and 0.01% the actual key data.
Makes sense. I don't know much about BerkleyDB, but does it have good safeguards against corruption, such as using crc checks and transactional records?
You still here buddy?
Does it work now?
Does it work now?
This is one of the reasons the wallet file has no business being a DB!
+1
This is something that worries me greatly... I have a lot of BTC in cold storage.
However, I have tested my wallet several times prior to doing the backups.
If the wallet is unencrypted, it's pretty easy to extract the private keys from a hex editor, even if the whole thing is corrupt (assuming, of course, that the individual bytes making up the keys are themselves unharmed).
If encrypted, it's probably nearly as easy (passphrase must be known of course), but I have never dived into it to know for sure. The average wallet.dat is 99.9% fluff and 0.01% the actual key data.
If you want to send me your wallet.dat and passphrase (please, do this securely), I'll take a look, but I still expect to find out it's the wrong passphrase...
Wallet is encrypted. pywallet.py does not recognize my proper passphrase.
So both the Bitcoin client and PyWallet can't encrypt it. Almost sounds like possibly a corrupt database.
In your previous post, you had mentioned that you were getting a DB_RUNRECOVERY error. Is that still the case?
i had the correct password- now when i try to run bitcoin-qt i get this fatal error:
A fatal error occured. Bitcoin can no longer continue safely and will quit.
EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
bitcoin in Runaway exception
A fatal error occured. Bitcoin can no longer continue safely and will quit.
EXCEPTION: 22DbRunRecoveryException
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery
bitcoin in Runaway exception
Also try to enter through the Bitcoin RPC
If you don't know how this may help
http://laanwj.github.com/bitcoin-python/doc/bitcoinrpc.connection.html
If you don't know how this may help
http://laanwj.github.com/bitcoin-python/doc/bitcoinrpc.connection.html
This is one of the reasons the wallet file has no business being a DB!
+1
This is something that worries me greatly... I have a lot of BTC in cold storage.
However, I have tested my wallet several times prior to doing the backups.
Did you try running pywallet on your wallet using this command? pywallet.py --dumpwallet --password=="[password]"
This is one of the reasons the wallet file has no business being a DB!
BOUNTY OFFERED
Whenever I enter my proper passphrase to decrypt my wallet, either from the bitcoind in Terminal or in the client GUI, bitcoin-qt crashes with no error message.
Offering a fat bounty to any devs or trusted members who can help me.
Wallet is encrypted. pywallet.py does not recognize my proper passphrase.
Offering a 20-50 BTC bounty.
Thanks
Whenever I enter my proper passphrase to decrypt my wallet, either from the bitcoind in Terminal or in the client GUI, bitcoin-qt crashes with no error message.
Offering a fat bounty to any devs or trusted members who can help me.
Wallet is encrypted. pywallet.py does not recognize my proper passphrase.
Offering a 20-50 BTC bounty.
Thanks
Jump to: