Armory not always giving latest balance

[tpofo]

I am not sure if other people are getting this issue.  I have read on here and it doesn't seem exactly posted as I am experiencing it.
I have to say I love Armory Bitcoin wallet.  There is no other wallet out there that comes close.  It has all the features I want and the trust and security I want.
So, I use it no matter if it is buggy sometimes because I still trust it.  I found the older versions were more rock solid in terms of giving current balances and transactions.  But, the newer version works much much faster with its own database.  The old one took about the same as the bitcoin core.  The new one is very small.  SO that is a major plus.

The problem I have is that sometimes(it happens randomly) it does not give me current balance although I verified it has downloaded all blocks and is current.  I tried it 2 ways.  I sync it with core first, then load Armory.  I also try just letting Armory do it with bitcoind.  Both ways sometimes(maybe 1 out of 10 times or so) will not give me current balance.

I get this from the console and it halts with no other lines.

Code:

-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads

The way I can get around this issue is to only rescan and rebuild armory database.  Then, I have current balance.  Why is my armory not 100% robust and flawless in scanning database when I load it?

[1714064135]

1714064135

[1714064135]

1714064135

[1714064135]

1714064135

[achow101]

Can you please post your log files?

What version of Armory are you using? What version of Bitcoin Core?

Why is my armory not 100% robust and flawless in scanning database when I load it?

Because all software has bugs and Armory doesn't have a lot of developers. There are only 3 developers that actively work on Armory, and only one does so full time. This means that there is a lack of testing and review so bugs usually slip through into releases.

[tpofo]

I'm using bitcoin core 0.14.2 and Armory 0.96.0

I attached the logs.  Note:  The dblog.txt file was weird and seemed binary and then at the bottom of it was text.  I copy just the text portion.  There doesn't seem to be the capture of the time it didnt work.  Not sure if it tells you anything.

Thanks for the help in advance.

armorylog.txt:
https://pastebin.com/W0mnjAxF

dbLog.txt:

Code:

Log file opened at 1499193957: e:\Armory/dbLog.txt
-INFO  - 1499193957: (..\main.cpp:23) Running on 8 threads
-INFO  - 1499193957: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1499193957: (..\BlockUtils.cpp:907) blkfile dir: E:\Bitcoin\blocks
-INFO  - 1499193957: (..\BlockUtils.cpp:908) lmdb dir: e:\Armory\databases
-INFO  - 1499193957: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1499193959: (..\BDM_Server.cpp:996) registered bdv: a681cb1c355f423c36c7
-INFO  - 1499193961: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1499193961: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 1499193968: (..\DatabaseBuilder.cpp:208) Found 474169 headers in db
-INFO  - 1499193971: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1499193975: (..\DatabaseBuilder.cpp:268) parsed block file #923
-INFO  - 1499193975: (..\DatabaseBuilder.cpp:268) parsed block file #924
-DEBUG - 1499193975: (..\Blockchain.cpp:242) Organizing chain 
-INFO  - 1499193975: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 4.345s
-INFO  - 1499193975: (..\DatabaseBuilder.cpp:106) scanning new blocks from #474147 to #474146
-INFO  - 1499193976: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1499193976: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 1499193976: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.025s
-INFO  - 1499193976: (..\DatabaseBuilder.cpp:160) init db in 14.702s
-INFO  - 1499193976: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking 
-INFO  - 1499193996: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 1499194001: (..\BlockchainScanner.cpp:650) scanned from height #474147 to #474148
-INFO  - 1499194025: (..\BlockchainScanner.cpp:650) scanned from height #474149 to #474153
-INFO  - 1499194026: (..\BlockchainScanner.cpp:650) scanned from height #474154 to #474154
-INFO  - 1499194035: (..\BlockchainScanner.cpp:650) scanned from height #474155 to #474155
-INFO  - 1499194044: (..\BlockchainScanner.cpp:650) scanned from height #474156 to #474159
-INFO  - 1499194049: (..\BlockchainScanner.cpp:650) scanned from height #474160 to #474161
-INFO  - 1499194050: (..\BlockchainScanner.cpp:650) scanned from height #474162 to #474174
-ERROR - 1499194068: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1499194068: (..\BlockDataMap.cpp:80)    header has: 22341d21d654bb52303833ad2ddc84df3cee666a3244c4a4e451f8c1e44d1503
-ERROR - 1499194068: (..\BlockDataMap.cpp:81)    block yields: 0cc9a1542175e6e37d71012a32f67194d8b2eaed6fc9282f45b7e63d65a289f0
-ERROR - 1499194068: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
-INFO  - 1499194068: (..\BlockchainScanner.cpp:650) scanned from height #474175 to #474175
-INFO  - 1499194069: (..\BlockchainScanner.cpp:650) scanned from height #474176 to #474176
-INFO  - 1499194072: (..\BlockchainScanner.cpp:650) scanned from height #474177 to #474192
-ERROR - 1499194089: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1499194089: (..\BlockDataMap.cpp:80)    header has: aaf537a845bd2b19c6d4b98d5da0ab3ace472290673a7e068083b2688e6fa571
-ERROR - 1499194089: (..\BlockDataMap.cpp:81)    block yields: ce563fd78c081e7acee397fd94fc845919f7f57007a53fe14c0f593d0391eedc
-ERROR - 1499194089: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
-INFO  - 1499194090: (..\BlockchainScanner.cpp:650) scanned from height #474193 to #474195
-ERROR - 1499194107: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1499194107: (..\BlockDataMap.cpp:80)    header has: c32795d3b32cd7f481c9943e5e36801e9eb0f1d8f50534fdb676555be09b5888
-ERROR - 1499194107: (..\BlockDataMap.cpp:81)    block yields: 4727e8272c9cada19c98405e36750217995e61492b9b3817fa35de0d5252ee27
-ERROR - 1499194107: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
-INFO  - 1499194108: (..\BlockchainScanner.cpp:650) scanned from height #474196 to #474207
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1499194121: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-INFO  - 1499194122: (..\BlockchainScanner.cpp:650) scanned from height #474208 to #474219
-INFO  - 1499194127: (..\BlockchainScanner.cpp:650) scanned from height #474220 to #474224
-WARN  - 1499194131: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN  - 1499194131: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN  - 1499194131: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-INFO  - 1499194131: (..\BlockchainScanner.cpp:650) scanned from height #474225 to #474226
-INFO  - 1499194387: (..\nodeRPC.cpp:368) Bitcoin server stopping
-ERROR - 1499194387: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 1499194387: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-INFO  - 1499194389: (..\BDM_Server.cpp:1025) unregistered bdv: a681cb1c355f423c36c7
-INFO  - 1499194389: (..\BDM_Server.cpp:936) proceeding to shutdown
-ERROR - 1499194390: (..\SocketObject.cpp:262) poll() error in readFromSocketThread: 10038
-ERROR - 1499194390: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: poll() error in readFromSocketThread: 10038
-INFO  - 1499194391: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-ERROR - 1499194392: (..\BDM_mainthread.cpp:286) caught exception in main thread: terminate

[achow101]

Do you have a log from a time that you saw this issue?

Also, it looks like you might have some corrupted blocks on disk as the dbLog.txt says that there is a merkle root mismatch. The only fix for corrupted blocks is to re-sync the entire blockchain.

[tpofo]

I will post again when it happens again.  I don't know what happened to dblog.txt I will delete and let it create a new one.  Not sure why it is weird looking and not just pure text.

As well, I will try syncing just before the corruption if possible.

[Onno]

I have a similar problem but for me balance is stuck at specific block 473295. It shows connected and that block no at bottom right.
Bitcoin Core RPC client version v0.14.1.0-g964a185
Armory 0.96-beta

I can start Bitcoin QT and then sync. It works just fine. Also in Armory no error messages but balance is not correct specifically it shows unconfirmed - less than six - but my transaction nows hundreds of confirmations.

No error messages in log files I think. Where should I look?

[tpofo]

I can start Bitcoin QT and then sync. It works just fine. Also in Armory no error messages but balance is not correct specifically it shows unconfirmed - less than six - but my transaction nows hundreds of confirmations.

I've tried many things.  What I found worked was to first launch bitcoin-qt and make sure it synced there correctly.  Then, exit that.  Start up armory and "rebuild and rescan" under help menu.  Then, restart armory.  This does go very quick with new db system in Armory.  These steps should have worked. Also, verify you are at latest block:   Check lower right corner in Armory block and compare it with the current block off a blockchain website to know latest.

---

As a follow up to achow101 help so far, I had some corruption in the blockchain as seen in the logs.  I painstakingly re-synced the bitcoin core from scratch.  It took 24 hours(approx. cumulative) on my computer.   I also deleted armory db and let it redo that.  I carefully looked at logs and everything seems very clean now.  In my case, although I am not 100% certain yet -- time will tell, the problem seems gone.  I will post again if I experience the "running ... zc parser threads" hang.