Amory says it's successfully connected but it's at an incorrect block height

[rainman01]

I know Armory takes a while to get going after you download the software as I've used it before, but it's never taken this long. I downloaded the blockchain just fine but then it took days to get through the organizing blockchain part (and I'm on a desktop with Intel i5 and 12 GB RAM). I'm on version 0.93.3 and running it on Windows 7. I've poured over the forums trying to figure out what is wrong and haven't found anything. When I woke up this morning it finally said connected and allowed me to restore my paper back up. I can see now that it is connected at an incorrect block height (244189 blocks).

I've always had issues with this software but have always been able to work through it, I've never had to pour in this much time and effort to get to my coin. Could anyone please help me resolve these issues? Thanks.

[1714866933]

1714866933

[1714866933]

1714866933

[1714866933]

1714866933

[achow101]

Shut down armory and then start up bitcoin core. Check that bitcoin core is fully up to sync or whether it is at the block height armory reports. If it isn't fully synced, wait for it to sync then shut it down and restart armory. If it is fully synced then there is an armory problem and for that we will need to armory logs.

[rainman01]

Core appears to be fully up to date but I don't know how to check the block height. It this something that can't be done through the UI?

[achow101]

Core appears to be fully up to date but I don't know how to check the block height. It this something that can't be done through the UI?

Go to Help > Debug Window and it will have somewhere that tells you the number of blocks it has.

[rainman01]

Okay it's up to date at block 395456.

Aromry appears to have come unstuck from block 244189 while organizing the blockchain (that's where it was last night before going to sleep).

Here's the end of the log file:

Log file opened at 1453993567: C:\Users\LenovoPC\AppData\Roaming\Armory\armorycpplog.txt
-INFO  - 1453993597: (..\BlockUtils.cpp:918) blkfile dir: C:\Users\LenovoPC\AppData\Roaming\Bitcoin\blocks
-INFO  - 1453993597: (..\BlockUtils.cpp:919) lmdb dir: C:\Users\LenovoPC\AppData\Roaming\Armory\databases
-INFO  - 1453993597: (..\lmdb_wrapper.cpp:478) Opening databases...
-INFO  - 1453993597: (..\BlockUtils.cpp:1250) Executing: doInitialSyncOnLoad
-INFO  - 1453993597: (..\BlockUtils.cpp:1321) Total number of blk*.dat files: 430
-INFO  - 1453993597: (..\BlockUtils.cpp:1322) Total blockchain bytes: 57,520,699,893
-INFO  - 1453993597: (..\BlockUtils.cpp:1695) Reading headers from db
-INFO  - 1453993607: (..\BlockUtils.cpp:1721) Found 395410 headers in db
-DEBUG - 1453993607: (..\Blockchain.cpp:211) Organizing chain w/ rebuild

Does "Found 395410 headers in db" mean it's up to block 395410? Right now it's still spinning on "organizing blockchain" but it says connected at 0 blocks at the bottom right corner.

[achow101]

Okay it's up to date at block 395456.

Aromry appears to have come unstuck from block 244189 while organizing the blockchain (that's where it was last night before going to sleep).

Here's the end of the log file:

Log file opened at 1453993567: C:\Users\LenovoPC\AppData\Roaming\Armory\armorycpplog.txt
-INFO  - 1453993597: (..\BlockUtils.cpp:918) blkfile dir: C:\Users\LenovoPC\AppData\Roaming\Bitcoin\blocks
-INFO  - 1453993597: (..\BlockUtils.cpp:919) lmdb dir: C:\Users\LenovoPC\AppData\Roaming\Armory\databases
-INFO  - 1453993597: (..\lmdb_wrapper.cpp:478) Opening databases...
-INFO  - 1453993597: (..\BlockUtils.cpp:1250) Executing: doInitialSyncOnLoad
-INFO  - 1453993597: (..\BlockUtils.cpp:1321) Total number of blk*.dat files: 430
-INFO  - 1453993597: (..\BlockUtils.cpp:1322) Total blockchain bytes: 57,520,699,893
-INFO  - 1453993597: (..\BlockUtils.cpp:1695) Reading headers from db
-INFO  - 1453993607: (..\BlockUtils.cpp:1721) Found 395410 headers in db
-DEBUG - 1453993607: (..\Blockchain.cpp:211) Organizing chain w/ rebuild

Does "Found 395410 headers in db" mean it's up to block 395410? Right now it's still spinning on "organizing blockchain" but it says connected at 0 blocks at the bottom right corner.

That is fine. It should be synced when it finishes.

[rainman01]

Is it normal for it to revert back? It's at 244189 now.

Log file opened at 1453994692: C:\Users\LenovoPC\AppData\Roaming\Armory\armorycpplog.txt
-INFO  - 1453994717: (..\BlockUtils.cpp:918) blkfile dir: C:\Users\LenovoPC\AppData\Roaming\Bitcoin\blocks
-INFO  - 1453994717: (..\BlockUtils.cpp:919) lmdb dir: C:\Users\LenovoPC\AppData\Roaming\Armory\databases
-INFO  - 1453994717: (..\lmdb_wrapper.cpp:478) Opening databases...
-INFO  - 1453994717: (..\BlockUtils.cpp:1250) Executing: doInitialSyncOnLoad
-INFO  - 1453994717: (..\BlockUtils.cpp:1321) Total number of blk*.dat files: 430
-INFO  - 1453994717: (..\BlockUtils.cpp:1322) Total blockchain bytes: 57,520,699,893
-INFO  - 1453994717: (..\BlockUtils.cpp:1695) Reading headers from db
-INFO  - 1453994719: (..\BlockUtils.cpp:1721) Found 395410 headers in db
-DEBUG - 1453994719: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN  - 1454011880: (..\BlockUtils.cpp:1351) --- Fetching SSH summaries for 1000 registered addresses
-WARN  - 1454011883: (..\BlockUtils.cpp:246) Couldn't find top block hash in last seen blk file. Searching for it further down the chain
-ERROR - 1454012160: (..\BlockUtils.cpp:639) Next block header found at offset 4737008
-WARN  - 1454012161: (..\BlockUtils.cpp:304) Inconsistent headers DB, attempting repairs
-INFO  - 1454012161: (..\BlockUtils.cpp:1364) Left off at file 0, offset 0
-INFO  - 1454012161: (..\BlockUtils.cpp:1367) Reading headers and building chain...
-INFO  - 1454012161: (..\BlockUtils.cpp:1368) Starting at block file 0 offset 0
-INFO  - 1454012161: (..\BlockUtils.cpp:1370) Block height 244189
-ERROR - 1454012241: (..\BlockUtils.cpp:639) Next block header found at offset 133270461
-ERROR - 1454012241: (..\BlockUtils.cpp:639) Next block header found at offset 4737008
-DEBUG - 1454012242: (..\Blockchain.cpp:211) Organizing chain w/ rebuild

[achow101]

Is it normal for it to revert back? It's at 244189 now.

Log file opened at 1453994692: C:\Users\LenovoPC\AppData\Roaming\Armory\armorycpplog.txt
-INFO  - 1453994717: (..\BlockUtils.cpp:918) blkfile dir: C:\Users\LenovoPC\AppData\Roaming\Bitcoin\blocks
-INFO  - 1453994717: (..\BlockUtils.cpp:919) lmdb dir: C:\Users\LenovoPC\AppData\Roaming\Armory\databases
-INFO  - 1453994717: (..\lmdb_wrapper.cpp:478) Opening databases...
-INFO  - 1453994717: (..\BlockUtils.cpp:1250) Executing: doInitialSyncOnLoad
-INFO  - 1453994717: (..\BlockUtils.cpp:1321) Total number of blk*.dat files: 430
-INFO  - 1453994717: (..\BlockUtils.cpp:1322) Total blockchain bytes: 57,520,699,893
-INFO  - 1453994717: (..\BlockUtils.cpp:1695) Reading headers from db
-INFO  - 1453994719: (..\BlockUtils.cpp:1721) Found 395410 headers in db
-DEBUG - 1453994719: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN  - 1454011880: (..\BlockUtils.cpp:1351) --- Fetching SSH summaries for 1000 registered addresses
-WARN  - 1454011883: (..\BlockUtils.cpp:246) Couldn't find top block hash in last seen blk file. Searching for it further down the chain
-ERROR - 1454012160: (..\BlockUtils.cpp:639) Next block header found at offset 4737008
-WARN  - 1454012161: (..\BlockUtils.cpp:304) Inconsistent headers DB, attempting repairs
-INFO  - 1454012161: (..\BlockUtils.cpp:1364) Left off at file 0, offset 0
-INFO  - 1454012161: (..\BlockUtils.cpp:1367) Reading headers and building chain...
-INFO  - 1454012161: (..\BlockUtils.cpp:1368) Starting at block file 0 offset 0
-INFO  - 1454012161: (..\BlockUtils.cpp:1370) Block height 244189
-ERROR - 1454012241: (..\BlockUtils.cpp:639) Next block header found at offset 133270461
-ERROR - 1454012241: (..\BlockUtils.cpp:639) Next block header found at offset 4737008
-DEBUG - 1454012242: (..\Blockchain.cpp:211) Organizing chain w/ rebuild

I'm not sure what is wrong then. Submit a bug report by going to Help > Submit Bug Report. The armory developers will be able to help you more. Also wait for goatpig to respond as he is one of the armory developers that is active on this forum.

[goatpig]

This is symptom of missing blocks. Armory found 390k or so headers that form an actual chain. Somewhere around ~244200, it pulled block data that is corrupt and the scan failed. That's handled poorly in 0.93.3 btw, sorry about that.

If it manages to progress past that block, you are all good. If the scanning process just hangs there, you will have to redownload the blockchain and start from scratch.

[rainman01]

Thanks to both of you for the responses. And it's no big deal, I was able to extract the private keys and sweep one of them with Electrum to get what I needed. The rest is still in Armory. I'll re-download and see if that helps because it seems to be stuck again on the same block.