"Organizing chain" on rebuild - How long should this take?

[tez02843]

I've been using Armory for 5-6 years, and I've had to delete my database folder several times and allow it to rebuild. It always takes a while, but I don't recall it ever taking as long as it is now. From "parsed block file #0" to "parsed block file #5039" took a little under 14 hours. Now it's been on "Organizing chain" for almost a full day.

My Bitcoin node is fully sycned (and working with other wallets), and Armory is running on an SSD (the blockchain is on an HDD). I'm running armorydb from the command line, with bitcoind running in the background.

My hardware is solid, and ArmoryDB has been using about 10-12% of my CPU. However, it's not writing anything to disk currently.

How long should I expect this to take? Or is something wrong?

[goatpig]

This sounds very slow. It shouldn't take over 2h for full DB build. Can you try with a fresh Armory databases folder and post logs?

[tez02843]

Code:

Log file opened at 06:09:08.000: C:\Users\Tez\AppData\Roaming/Armory/dbLog.txt
-INFO  - 06:09:08.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 12 threads
-INFO  - 06:09:08.016: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO  - 06:09:08.016: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: D:\bitcoin/blocks
-INFO  - 06:09:08.016: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: C:\Users\Tez\AppData\Roaming/Armory/databases
-INFO  - 06:09:08.016: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 06:09:08.032: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port 9001
-INFO  - 06:09:14.110: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 06:10:37.344: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-WARN  - 06:10:37.344: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:1241) No headers in DB yet!
-INFO  - 06:10:37.344: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 1 headers in db
-INFO  - 06:10:37.344: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO  - 06:10:40.563: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #0
...
-INFO  - 08:59:24.250: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #5043
-INFO  - 09:00:18.016: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain 

And it's been stuck there again for about 7 hours now.

[goatpig]

You likely have a long orphan, i.e. a block deep into the chain is missing, triggering 100k+ block reorgs over and over. I don't know how these happen, but I've ran into them myself recently.

This isn't an Armory issue per se, your copy of the chain is corrupted somehow. You will need to reindex Core first to fix the issue, Armory cannot help you here.

Call bitcoind/bitcoin-qt with -reindex and let it do its thing. Once it succeeds, you can wipe Armory's database folder and try again.

[tez02843]

I don't think that's it, I keep a known good copy of the blockchain on an external drive, then I copy it over when I'm ready to use it (I've had to re-sync too many times). When I did it this time, Armory worked fine at first, synced up and connected and showed my balance/transactions/etc., but was giving me an error when trying to send coins. That's why I deleted the database folder to begin with, but now no matter what I do, I can't get past "organizing chain". Even after using the old copy of the blockchain that was working fine previously. It's also working fine with my other wallet (Sparrow), I'm able to connect & send & receive no problem.

[goatpig]

Is ArmoryDB maxing a thread once it gets to "Organizing Chain"?