Bitcoin Forum

My Armory wallet has been preforming great up until now.

My normal process is to load the Bitcoin core and let it sync with the network. Once done, then I open the Armory wallet and it opens and it is ready to go.

Now it doesn't ever finish getting sync'd, it has stayed here (24 hours +) for some time:

https://imgur.com/a/w35HVa7

I have restarted the computer, core, and Armory as well.

Log files are located here:

Pastebin #1

https://pastebin.com/h31xgXKG

Pastebin #2

https://pastebin.com/rdYUvtTW

Ideas why this is stuck?

Thanks!

I would guess that the problem is related to your full node



Can you verify that your blocks are indeed stored in this directory?



Can you get core up and running without any problems?

Can you try to check if your bitcoin core is set to pruned mode?

Because if Bitcoin core is not fully synced armory will always experience some issue and it won't work correctly, and armory doesn't work on prune mode. That's why I suggest you check the bitcoin core first if it is pruned mode after if it's set to pruned mode better to disable it and then restart.


Useful links below, related to your issue.

- https://raw.githubusercontent.com/droark/BitcoinArmory/4e849daa861fc43f44d9910b6cce54d9cb8b4aec/ArmoryQt.py
- Armory stuck on "Preparing Databases (https://bitcointalk.org/index.php?topic=5179186.20)
- Unable to get db to load (https://bitcointalk.org/index.php?topic=5133191.0)

Your files show you're running Armory Version 0.96.4 - this is not the newest Armory release. 

Have you tried Armory Version 0.96.5?

Thanks for everybody's help I will look into this and post what I find.

2020-06-26 13:49:21 (ERROR) -- ArmoryQt.py:1198 - 3 attempts to load blockchain failed.  Remove mempool.bin.

C:\\Users\\Owner\\AppData\\Roaming\\Bitcoin\\blocks

Log shows client is failing to talk to the DB. You should first update to 0.96.5.

That's fine.
But there are morethan just those 10 block files, right? How large is the whole blocks folder?



And also, can you confirm that you are using the latest version / have upgraded (https://btcarmory.com/ (https://btcarmory.com/))?

Block folder is 302GB, with numerous block files.

I have not upgraded to the latest version but I will now.

Thanks

Ok I have updated both Armory and bitcoin core to the latest versions. Now when I attempt to sync the Armory software it gets stuck at 100% on all 3 files (node status, build databases, resolving TX hashes).

see photo

https://imgur.com/UckvTts

Here is the new log files, broken into 2 files as paste bin will no longer allow a complete file up load, (for a file this size)

Paste 1

https://pastebin.com/WujSddjc

Paste 2

https://pastebin.com/xn0YJDP6

Ideas where the error lies?

There's too much stuff mixed up in the logs. Delete them, start Armory again and post armoryqt.txt along with dbLog.txt.

You'll find the logs here: C:\Users\Owner\AppData\Roaming\Armory\

Just to be 100% sure, when you run Bitcoin Core, what value is displayed as your "blocksdir" when you open "Window - Information"? ???

If that says C:\Users\Owner\AppData\Roaming\Bitcoin\blocks then that setting is just fine...


It's quite possible, that running the older version has resulted in some incompatibilities in the Armory database(s)... You can try the "Rebuild and Rescan Databases" option from the Help menu in Armory and then restart.

Thank you for your help HCP!


In regards to your questions:

Just to be 100% sure, when you run Bitcoin Core, what value is displayed as your "blocksdir" when you open "Window - Information"? Huh

If that says C:\Users\Owner\AppData\Roaming\Bitcoin\blocks then that setting is just fine... YES that is what is shows


It's quite possible, that running the older version has resulted in some incompatibilities in the Armory database(s)... You can try the "Rebuild and Rescan Databases" option from the Help menu in Armory and then restart.

Will try that next

In that case, your "pathing" is more than likely going to be "OK"... and Armory is looking in the correct directory for the block data that it needs. So, I'm fairly certain it is just a corrupted database.


Don't forget to report back with the results! ;)

Good news to report!

It works!

The rebuild/sync mode on Armory seems to solve the issues.

Thanks everybody!