Bitcoin Forum
July 28, 2017, 05:02:43 AM *
News: BIP91 seems stable: there's probably only slightly increased risk of confirmations disappearing. You should still prepare for Aug 1.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Bitcoin-qt crashes, need help exporting my private keys to new wallet  (Read 3104 times)
ez1btc
Newbie
*
Offline Offline

Activity: 14


View Profile
May 16, 2012, 01:57:21 AM
 #1

After encrypting my wallet on the Bitcoin client, it started to crash every time i entered the correct passphrase. After upgrading to 0.6.2 I am unable to start bitcoin-qt at all. How can I extract my private keys from the bitcoin client on my computer (wallet.dat?) so I can import them to a new wallet?

 *A thorough explanation of how to find my private keys within my wallet dump would help, as I have dumped my wallet using the web interface of pywallet.py*
 
I'm a relative newbie to Linux and working to familiarize myself with how it works- having a tiny bit of trouble wading through the command line interface. thanks in advance for any help!
1501218163
Hero Member
*
Offline Offline

Posts: 1501218163

View Profile Personal Message (Offline)

Ignore
1501218163
Reply with quote  #2

1501218163
Report to moderator
1501218163
Hero Member
*
Offline Offline

Posts: 1501218163

View Profile Personal Message (Offline)

Ignore
1501218163
Reply with quote  #2

1501218163
Report to moderator
1501218163
Hero Member
*
Offline Offline

Posts: 1501218163

View Profile Personal Message (Offline)

Ignore
1501218163
Reply with quote  #2

1501218163
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1501218163
Hero Member
*
Offline Offline

Posts: 1501218163

View Profile Personal Message (Offline)

Ignore
1501218163
Reply with quote  #2

1501218163
Report to moderator
1501218163
Hero Member
*
Offline Offline

Posts: 1501218163

View Profile Personal Message (Offline)

Ignore
1501218163
Reply with quote  #2

1501218163
Report to moderator
1501218163
Hero Member
*
Offline Offline

Posts: 1501218163

View Profile Personal Message (Offline)

Ignore
1501218163
Reply with quote  #2

1501218163
Report to moderator
Stephen Gornick
Legendary
*
Offline Offline

Activity: 2212



View Profile
May 16, 2012, 02:02:41 AM
 #2

I remember someone else had this problem recently but it was resolved after getting a new blockchain or something like that.  [Update: Read luke-jr's suggestion first.]

It wouldn't hurt to try starting the client with -rescan.

If that doesn't fix it, try removing the blk*.dat from your data directory and restart.

Or, for testing purposes a quicker method to get a copy of the blockchain is to download a recent blockchain binary download:
 - http://bitcoin.stackexchange.com/questions/3551

As far as importing into a new wallet, v0.6.x as importprivkey:
 - http://en.bitcoin.it/wiki/Importprivkey

Luke-Jr
Legendary
*
Offline Offline

Activity: 2226



View Profile
May 16, 2012, 02:06:05 AM
 #3

I know for the 2 cases I've heard of this crash, it turned out to be a rare case where the wrong password was being accepted erroneously, which then led to a crash. So for every good password, there were maybe 0.4% of all wrong passwords that crashed instead of giving an error. Reconsider whether you actually have the right password.

ez1btc
Newbie
*
Offline Offline

Activity: 14


View Profile
May 16, 2012, 02:07:49 AM
 #4

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
Stephen Gornick
Legendary
*
Offline Offline

Activity: 2212



View Profile
May 30, 2012, 11:03:42 PM
 #5

Bookend for this thread ... continued here:

 - http://bitcointalk.org/index.php?topic=84409.0

swissmate
Sr. Member
****
Offline Offline

Activity: 280



View Profile
May 31, 2012, 08:17:05 AM
 #6

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


 
 
           ▄████▄
         ▄████████▄
       ▄████████████▄
     ▄████████████████▄
    ████████████████████      ▄█▄                 ▄███▄                 ▄███▄                 ▄████████████████▀   ▄██████████

  ▄▄▄▀█████▀▄▄▄▄▀█████▀▄▄▄     ▀██▄             ▄██▀ ▀██▄             ▄██▀ ▀██▄             ▄██▀                   ██
▄█████▄▀▀▀▄██████▄▀▀▀▄█████▄     ▀██▄         ▄██▀     ▀██▄         ▄██▀     ▀██▄         ▄██▀        ▄█▄          ▀██████████████▄
████████████████████████████       ▀██▄     ▄██▀         ▀██▄     ▄██▀         ▀██▄     ▄██▀          ▀█▀                        ██
 ▀████████████████████████▀          ▀██▄ ▄██▀             ▀██▄ ▄██▀     ▄█▄     ▀██▄ ▄██▀                                       ██
   ▀████████████████████▀              ▀███▀                 ▀███▀       ▀█▀       ▀███▀      ▄███████████████████████████████████▀
     ▀████████████████▀
       ▀████████████▀
         ▀████████▀
           ▀████▀
║║


║║
.
.

║║
██
║║
.
.

║║
██
║║
.
║║


║║
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!