Topic: Retrieve private keys for online-generated address (Read 1229 times)

All of yo look like you have malformed blocks in your local copy of the blockchain. You're gonna have to delete it and redownload it.

wheeler: As for your private keys, you can use the new backup center feature to extract your private keys in version 0.90. Make sure to start it in Expert mode, then go to your wallet properties, pick 'Backup Wallet' then 'Export Key List'

I got the same error "Cannot get tx copy, because don't have full StoredTx!"

Log file opened at 1391416017: C:\Users\Admin\AppData\Roaming\Armory\armorycpplog.txt
-INFO  - 1391416018: (..\BlockUtils.cpp:1582) Set home directory:
-INFO  - 1391416018: (..\BlockUtils.cpp:1604) Set blkfile dir: C:\Users\Admin\AppData\Roaming\Bitcoin\blocks
-INFO  - 1391416018: (..\BlockUtils.cpp:1614) Set leveldb dir: C:\Users\Admin\AppData\Roaming\Armory\databases
-INFO  - 1391416018: (..\BlockUtils.cpp:1570) SetBtcNetworkParams
-INFO  - 1391416018: (..\BlockUtils.cpp:3564) Executing: doInitialSyncOnLoad
-INFO  - 1391416018: (..\BlockUtils.cpp:3604) Number of registered addr: 177
-INFO  - 1391416018: (..\leveldb_wrapper.cpp:127) Opening databases...
-INFO  - 1391416029: (..\BlockUtils.cpp:1695) Total blk*.dat files:                 113
-INFO  - 1391416029: (..\BlockUtils.cpp:1713) Current Top block in HEADERS DB:  283914
-INFO  - 1391416029: (..\BlockUtils.cpp:1714) Current Top block in BLKDATA DB:  283914
-INFO  - 1391416029: (..\BlockUtils.cpp:1715) Current Applied blocks up to hgt: 0
-INFO  - 1391416034: (..\BlockUtils.cpp:1816) First unrecognized hash file:       112
-INFO  - 1391416034: (..\BlockUtils.cpp:1817) Offset of first unrecog block:      35756123
-INFO  - 1391416034: (..\BlockUtils.cpp:1826) First blkfile not in DB:            112
-INFO  - 1391416034: (..\BlockUtils.cpp:1827) Location of first block not in DB:  35756123
-INFO  - 1391416034: (..\BlockUtils.cpp:3646) Fetching stored script histories from DB
-INFO  - 1391416034: (..\BlockUtils.cpp:3690) Reading all headers and building chain...
-INFO  - 1391416056: (..\BlockUtils.cpp:3695) Total number of blk*.dat files: 113
-INFO  - 1391416056: (..\BlockUtils.cpp:3696) Total number of blocks found:   283918
-INFO  - 1391416056: (..\BlockUtils.cpp:3708) Getting latest blocks from blk*.dat files
-INFO  - 1391416056: (..\BlockUtils.cpp:3709) Total blockchain bytes: 15,071,006,966
-INFO  - 1391416056: (..\BlockUtils.cpp:3715) Parsing blockchain file: C:\Users\Admin\AppData\Roaming\Bitcoin\blocks/blk00112.dat
-INFO  - 1391416056: (..\BlockUtils.cpp:3812) C:\Users\Admin\AppData\Roaming\Bitcoin\blocks/blk00112.dat is 50,331,648 bytes
-INFO  - 1391416079: (..\BlockUtils.cpp:3729) Processed 4 raw blocks DB (22 seconds)
-INFO  - 1391416079: (..\BlockUtils.cpp:3758) Starting scan from block height: 0
-ERROR - 1391416662: (..\StoredBlockObj.cpp:1063) Cannot get tx copy, because don't have full StoredTx!

I got the same thing after a system crash!

Armory starts initializing the DB it goes to 100% and then the application just disappears completely.



I'll try the --rebuild option 1st.

How did it go on your side Wheeler ?

Thanx,

Thanks for the suggestion, giving --rebuild a try now.

Ack!  That's an error I haven't seen yet.  Can you try starting Armory again but using the "--rebuild" flag.  Sounds like the database somehow got corrupted.  So far, I have seen it safely recover from being restarted while building the database, but it may not be reliable -- it looks like your system may have interrupted the initial database build (since it says 65k raw blocks added, not 260k blocks). 

Obviously it should be robust, but those are things that will take some time to iron out.  Until then, can you simply wait through another --rebuild and let me know if you get the same problem?  People have actually tested it on 12.04 with 2GB of RAM, so I know it's possible to work

I've not needed to move BTC for a while and now I'm revisiting, I'm having a lot of problems getting Armory running on my online machine (mostly since it's a tad under-specced @ 2GB RAM).

I use cold-storage, and I've got coins in an address that was created online, but the offline wallet has never had to sign txns for it.  As a workaround, is there any way I can derive the private key on the offline machine for the online-generated address, to let me use an alternate client?

As a side-point, I've also tried the new testing branch, but that has problems after scanning the blocks, throwing a segfault...


Any assistance greatly appreciated!