Bitcoin Forum

Bitcoin => Armory => Topic started by: noamm1 on September 15, 2017, 03:32:56 PM



Title: Bitcoin Armory is not updated with the latest block in the blockchain
Post by: noamm1 on September 15, 2017, 03:32:56 PM
Hey,

I'm new to armory wallet.
I just downloaded bitcoin core and armory wallet.
now I see that armory is connected with 481574 blocks although in blockchain.info I see that the latest block is 485414

How can I sync Armory with the latest blocks.

The problem is that, i have an input transaction in block 485278 and therefore I can't see it in my wallet.

How can I sync my armory with the latest blocks ??
Thanks.


Title: Re: Bitcoin Armory is not updated with the latest block in the blockchain
Post by: achow101 on September 15, 2017, 03:35:13 PM
Armory relies on Bitcoin Core. Bitcoin Core must be running and be synced in order for Armory to be synced. Is Bitcoin Core running (Armory will usually run it for you) and fully synced?


Title: Re: Bitcoin Armory is not updated with the latest block in the blockchain
Post by: noamm1 on September 15, 2017, 03:50:16 PM
Thanks for the fast reply.

My Bitcoin core is not running in parallel to the armory (it gives me error when trying to run both of them together) but the bitcoin core is indeed updated with the latest blocks from today.
What should I do?


Title: Re: Bitcoin Armory is not updated with the latest block in the blockchain
Post by: achow101 on September 15, 2017, 04:11:54 PM
Thanks for the fast reply.

My Bitcoin core is not running in parallel to the armory (it gives me error when trying to run both of them together) but the bitcoin core is indeed updated with the latest blocks from today.
What should I do?
Run Bitcoin Core manually. First stop both Bitcoin Core and Armory. Then start Armory and go to File > Settings and uncheck the option "Let Armory run Bitcoin Core in the background". Then stop Armory. Start Bitcoin Core and let it fully sync. Then start Armory again.


Title: Re: Bitcoin Armory is not updated with the latest block in the blockchain
Post by: noamm1 on September 17, 2017, 10:19:17 AM
Thanks for your reply.

I managed to solve the problem.

Solution:
rebuild and rescan database.

Thanks for the help man.