Armory (0.95.1) not showing any transaction history or balance

[norulezapply]

Hi,

I have been using Armory for a few years now and with the recent update I am unfortunately losing faith with the software after a multitude of problems. Here's what I have tried:

On my main Windows 7 PC, I had Bitcoin 0.13.2 installed and fully synced. I had an old version of Armory so updated to 0.95.1. I let Armory rebuild the databases, which used all of my RAM to the point where the PC became completely unusable (never used to do this before). I left Armory building databases overnight and over several sessions but it never finished.

I tried clearing down the Bitcoin DB and Armory DB, re-synchronised the entire Bitcoin history. Started Armory rebuilding the databases again. This time it got to near completion (to scanning transaction history), and then crashed. When I started it back up again it just started rebuilding the database from the beginning.

I tried running Bitcoin Core separately, still no luck. (NOTE: I was using --datadir option for Armory and Bitcoin. Doesn't seem to be fully supported by ArmoryDB.exe, as it still looks in %appdata% for the Bitcoin blocks...)


So to start clean I installed Bitcoin on an entirely new Windows 7 64bit machine. I let it fully sync with the network.
Installed Armory 0.95.1.
Set Armory NOT to run Bitcoin core, so I have the Bitcoin Core GUI and Armory GUI running separately.
Launched Bitcoin core, launched armory.
Waited for Armory to build the databases, which was very quick compared to last time.

Armory now tells me that it has Connected (451995 blocks), whereas Bitcoin tells me it is fully synced at 452007. But I can see ArmoryDB is still scanning in the background.


The problem now is that Armory is showing no transaction history at all for my wallet and saying the balance is 0.


The log files are here:
http://textuploader.com/d1x4o
http://textuploader.com/d1x4d
http://textuploader.com/d1x4t

I hope most of these problems are solved in the next version. Armory was always a fantastic piece of software.

Best Regards

[achow101]

Firstly, when you started Armory, did you get a cmd window? If you did, don't close it, that's ArmoryDB and it must be running.

Secondly, to set custom datadirs, Bitcoin Core needs to have --datadir. Armory needs to have --datadir for its own data directory which is not the same as Bitcoin Core's. In order to tell it where Bitcoin Core's datadir is, you need to use --satoshi-datadir.

If you did not delete the databases directory inside Armory's datadir at some point already, I suggest that you stop Armory and do that now. Even if you did, I think you should do that again to force a rebuild and rescan. The new Armory databases build much faster than the old ones and are much smaller.

Whilst ArmoryDB is building the db again, watch that there are no errors being reported in the cmd window (which the dbLog.txt mirrors). If there are, please report back with the full dbLog.txt again. Also check that it actually scans all the block files and all of the blocks.

[norulezapply]

Firstly, when you started Armory, did you get a cmd window? If you did, don't close it, that's ArmoryDB and it must be running.

Secondly, to set custom datadirs, Bitcoin Core needs to have --datadir. Armory needs to have --datadir for its own data directory which is not the same as Bitcoin Core's. In order to tell it where Bitcoin Core's datadir is, you need to use --satoshi-datadir.

If you did not delete the databases directory inside Armory's datadir at some point already, I suggest that you stop Armory and do that now. Even if you did, I think you should do that again to force a rebuild and rescan. The new Armory databases build much faster than the old ones and are much smaller.

Whilst ArmoryDB is building the db again, watch that there are no errors being reported in the cmd window (which the dbLog.txt mirrors). If there are, please report back with the full dbLog.txt again. Also check that it actually scans all the block files and all of the blocks.

Thank you for the suggestions.

I did indeed get the cmd window (ArmoryDB.exe) and have left it running all times I've tried Armory.

Ah, thanks. It's a bit confusing as when you choose to run Bitcoin Core separately from Armory, the option to input a Bitcoin Core data dir in the GUI gets disabled, and ArmoryDB tries to look in the default location. This should really still be enabled.

I went ahead and deleted the databases folder inside Armory. I'm running it from my main PC again now, with Bitcoin set to run as part of Armory. I'm using --datadir and --satoshi-datadir flags on ArmoryQt.exe.

It has been building databases for about 4 hours. It says it is 20% through. When I came back to my PC it was pretty frozen up and unusable, and I had to Ctrl-C on the ArmoryDB window as I couldn't get to the quit option in Armory for the lag. Just to note, I'm running an AMD FX 8350 (8 cores, ~4.0GHz) with 12GB DDR3.

Is there a way to stop it consuming all of the memory/CPU? And does 4 hours for 20% sound right (based off your previous comment that it is much faster now)?

(I see "Running on 8 threads" and "Ram usage level 4" in the DB log but I don't know where I can set the RAM usage level)

Thanks

[MrRog]

Hello
I have the same problem...
In cmd I see this when I creat the db new

ERROR - 1486617937: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1486617937: (..\BlockDataMap.cpp:80)    header has: xxx
-ERROR - 1486617937: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
-INFO  - 1486617937: (..\DatabaseBuilder.cpp:268) parsed block file #278
-DEBUG - 1486617937: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1486617947: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 682.79s
-INFO  - 1486617947: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
-ERROR - 1486617947: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1486617947: (..\BlockDataMap.cpp:80)    header has: xxx
-ERROR - 1486617947: (..\BlockDataMap.cpp:81)    block yields:xx
-ERROR - 1486617947: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root

how I can fix this...  or better question how I get my BTC :-(
regards

[norulezapply]

Hello
I have the same problem...
In cmd I see this when I creat the db new

ERROR - 1486617937: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1486617937: (..\BlockDataMap.cpp:80)    header has: xxx
-ERROR - 1486617937: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
-INFO  - 1486617937: (..\DatabaseBuilder.cpp:268) parsed block file #278
-DEBUG - 1486617937: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1486617947: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 682.79s
-INFO  - 1486617947: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
-ERROR - 1486617947: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1486617947: (..\BlockDataMap.cpp:80)    header has: xxx
-ERROR - 1486617947: (..\BlockDataMap.cpp:81)    block yields:xx
-ERROR - 1486617947: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root

how I can fix this...  or better question how I get my BTC :-(
regards

Hi, please don't thread hijack, but it sounds like your Bitcoin Core database or Armory database might be corrupt and need rebuilding.

[MrRog]

Hello
I have rebuild and rescan.. but same problem.... I try again...
Same Problem I delete everithing and Install from scratch....

[goatpig]

Hello
I have rebuild and rescan.. but same problem.... I try again...
Same Problem I delete everithing and Install from scratch....

Hello
I have the same problem...
In cmd I see this when I creat the db new

ERROR - 1486617937: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1486617937: (..\BlockDataMap.cpp:80)    header has: xxx
-ERROR - 1486617937: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root
-INFO  - 1486617937: (..\DatabaseBuilder.cpp:268) parsed block file #278
-DEBUG - 1486617937: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1486617947: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 682.79s
-INFO  - 1486617947: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
-ERROR - 1486617947: (..\BlockDataMap.cpp:79) merkle root mismatch!
-ERROR - 1486617947: (..\BlockDataMap.cpp:80)    header has: xxx
-ERROR - 1486617947: (..\BlockDataMap.cpp:81)    block yields:xx
-ERROR - 1486617947: (..\DatabaseBuilder.cpp:353) block deser except: invalid merkle root

how I can fix this...  or better question how I get my BTC :-(
regards

Create your own thread, post both armorylog.txt and dbLog.txt in full.

[norulezapply]

Hi again,

Following on from my last post, I continued running Armory again today for another 4 hours or so.

This time again it says only 22% of the way through building Armory databases with 2 minutes remaining (of course this is inaccurate as it always gives these low figures).

Same problem with it using up all the RAM and making the machine unusable.

Is there a way to lower the RAM usage level?

Thanks

[achow101]

Hi again,

Following on from my last post, I continued running Armory again today for another 4 hours or so.

This time again it says only 22% of the way through building Armory databases with 2 minutes remaining (of course this is inaccurate as it always gives these low figures).

Same problem with it using up all the RAM and making the machine unusable.

Is there a way to lower the RAM usage level?

Thanks

Start Armory with the --db-type=DB_BARE and --ram-usage=1 options set. You will need to delete the databases folder again as it will build a new, lighter database (and thus requiring less RAM and CPU to build).

[norulezapply]

Hi again,

Following on from my last post, I continued running Armory again today for another 4 hours or so.

This time again it says only 22% of the way through building Armory databases with 2 minutes remaining (of course this is inaccurate as it always gives these low figures).

Same problem with it using up all the RAM and making the machine unusable.

Is there a way to lower the RAM usage level?

Thanks

Start Armory with the --db-type=DB_BARE and --ram-usage=1 options set. You will need to delete the databases folder again as it will build a new, lighter database (and thus requiring less RAM and CPU to build).

Thank you. That sounds like what I was hoping for. Here are my command line settings now:

--datadir=J:\Armory --satoshi-datadir=J:\BTC --db-type=DB_BARE --ram-usage=1

I deleted the databases folder (also deleted the log files) and restarted Armory. Unfortunately I get the following error:

---------------------------
Database Error
---------------------------
Armory failed to spawn the DB!<br> Continuing operations in offline mode instead. <br> Refer to the dbLog.txt for more information.


When I look for dbLog.txt I see that no dbLog.txt was created..
However I found this in the armorylog.txt:


2017-02-12 15:05 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-02-12 15:05 (ERROR) -- ArmoryQt.py:2211 - Failed to start Armory database: cannot concatenate 'str' and 'int' objects
Traceback (most recent call last):
  File "ArmoryQt.py", line 2198, in startArmoryDBIfNecessary
  File "SDM.pyc", line 517, in spawnDB
TypeError: cannot concatenate 'str' and 'int' objects
2017-02-12 15:05 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 0
2017-02-12 15:07 (INFO) -- ArmoryQt.py:5597 - Dashboard switched to user-OfflineOnlinePoss

[norulezapply]

Hi again.

I tried running ArmoryDB.exe manually with the same parameters:

ArmoryDB.exe --datadir=J:\Armory --satoshi-datadir=J:\BTC --db-type=DB_BARE --ram-usage=1

This worked and appeared to set the RAM usage to 1, but I still had the same problem where it would use up all my RAM to the point where the computer became unusable.

Any ideas?

Thanks

[creamers]

Think goatpig solved this in his latest test release..check it out

[pingdrive]

I've had the same issue (no transactions shown, zero balance being shown) for a week or so. I've rebuilt the database a couple of times and it always freezes around 50%. I've downloaded the newest binary I can find (armory_0.96.0.2-testing_amd64.deb) and will report results.

System:

- i7, fast CPU
- 32 GB RAM
- Linux Mint 18.1
- Amory 0.96 (latest official)
- Bitcoin 0.14.1 (latest official)

Results

Indexed to 63%, then stuck. bitcoind uses a 1 GB RAM and lots of CPU.

dbLog.txt has:

Code:

-INFO  - 11:45:23: (DatabaseBuilder.cpp:268) parsed block file #571
-INFO  - 11:45:27: (DatabaseBuilder.cpp:268) parsed block file #572
-INFO  - 11:45:30: (DatabaseBuilder.cpp:268) parsed block file #573
-INFO  - 11:45:31: (SocketObject.cpp:350) POLLIN recv return 0
-ERROR - 11:45:31: (BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 11:45:31: (BitcoinP2P.cpp:969) Disconnected from Bitcoin node

armorylog.txt has congruent info:

Code:

2017-06-12 11:45:16 (INFO) -- ArmoryQt.py:4609 - Dashboard switched to "Scanning" mode
2017-06-12 11:45:20 (INFO) -- ArmoryQt.py:4609 - Dashboard switched to "Scanning" mode
2017-06-12 11:45:23 (INFO) -- ArmoryQt.py:4609 - Dashboard switched to "Scanning" mode
2017-06-12 11:45:27 (INFO) -- ArmoryQt.py:4609 - Dashboard switched to "Scanning" mode
2017-06-12 11:45:31 (INFO) -- ArmoryQt.py:4609 - Dashboard switched to "Scanning" mode
2017-06-12 12:03:35 (INFO) -- ArmoryQt.py:5392 - BDM state is scanning -- force shutdown BDM
2017-06-12 12:03:35 (INFO) -- SDM.py:456 - Called stopBitcoind
2017-06-12 12:03:35 (ERROR) -- ArmoryQt.py:5405 - Strange error during shutdown
Traceback (most recent call last):
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 5396, in closeForReal
    TheSDM.stopBitcoind()
  File "/usr/lib/armory/SDM.py", line 482, in stopBitcoind
    LOGERROR(e)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 828, in LOGERROR
    logging.error(callerStr + logstr)
TypeError: cannot concatenate 'str' and 'exceptions.RuntimeError' objects
2017-06-12 12:03:35 (INFO) -- ArmoryQt.py:5407 - Attempting to close the main window!

I.e. around 11:45 there was some problem with the Armory and bitcoind communication that caused a freeze.

Second testing

I tried the 'run Bitcoin Core yourself' approach. I disable the "let Armory run bitcoind" option. Then I delete the

Code:

.armory/Databases directory

. And then I start Armory. It rebuilds the database. However, it finishes at a too low block (195969 vs. Bitcoin Core's 470992). And no transaction history or balance.


dbLog.txt

Code:

Log file opened at 19:45:37: /home/me/.armory/dbLog.txt
-INFO  - 19:45:37: (main.cpp:29) Running on 4 threads
-INFO  - 19:45:37: (main.cpp:30) Ram usage level: 4
-INFO  - 19:45:37: (BlockUtils.cpp:907) blkfile dir: /home/me/.bitcoin/blocks
-INFO  - 19:45:37: (BlockUtils.cpp:908) lmdb dir: /home/me/.armory/databases
-INFO  - 19:45:37: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 19:45:37: (BDM_Server.h:248) Listening on port 53271
-INFO  - 19:45:37: (BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 19:45:37: (DatabaseBuilder.cpp:169) Reading headers from db
-WARN  - 19:45:37: (lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO  - 19:45:37: (DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO  - 19:45:37: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 19:45:38: (BDM_Server.cpp:1021) registered bdv: 4ba6700ae9e71bd3c3cc
-INFO  - 19:45:38: (BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 19:45:42: (DatabaseBuilder.cpp:268) parsed block file #1
-INFO  - 19:45:44: (DatabaseBuilder.cpp:268) parsed block file #2
-INFO  - 19:45:45: (DatabaseBuilder.cpp:268) parsed block file #3
-INFO  - 19:45:46: (DatabaseBuilder.cpp:268) parsed block file #5
-INFO  - 19:45:46: (DatabaseBuilder.cpp:268) parsed block file #6
-INFO  - 19:45:47: (DatabaseBuilder.cpp:268) parsed block file #7
-INFO  - 19:45:48: (DatabaseBuilder.cpp:268) parsed block file #9
-INFO  - 19:45:49: (DatabaseBuilder.cpp:268) parsed block file #10
-INFO  - 19:45:50: (DatabaseBuilder.cpp:268) parsed block file #11
-INFO  - 19:45:51: (DatabaseBuilder.cpp:268) parsed block file #13
-INFO  - 19:45:52: (DatabaseBuilder.cpp:268) parsed block file #14
-INFO  - 19:45:52: (DatabaseBuilder.cpp:268) parsed block file #15
-INFO  - 19:45:53: (DatabaseBuilder.cpp:268) parsed block file #17
-INFO  - 19:45:54: (DatabaseBuilder.cpp:268) parsed block file #21
-DEBUG - 19:45:58: (Blockchain.cpp:242) Organizing chain 
-INFO  - 19:46:00: (DatabaseBuilder.cpp:56) updated HEADERS db in 36.2466s
-INFO  - 19:46:00: (BDM_supportClasses.cpp:1841) Enabling zero-conf tracking
-INFO  - 19:46:00: (BDM_supportClasses.cpp:366) Starting address registration process
-INFO  - 19:46:02: (BlockchainScanner.cpp:650) scanned from height #0 to #141742
-INFO  - 19:46:04: (BlockchainScanner.cpp:650) scanned from height #141743 to #169412
-INFO  - 19:46:06: (BlockchainScanner.cpp:650) scanned from height #169413 to #183002
-INFO  - 19:46:07: (BlockchainScanner.cpp:650) scanned from height #183003 to #186779
-INFO  - 19:46:08: (BlockchainScanner.cpp:650) scanned from height #186780 to #191629
-INFO  - 19:46:09: (BlockchainScanner.cpp:650) scanned from height #191630 to #195907
-INFO  - 19:46:09: (BlockchainScanner.cpp:650) scanned from height #195908 to #195969
-INFO  - 19:46:09: (BlockchainScanner.cpp:225) scanned transaction history in 14.3943s
-INFO  - 19:46:10: (BlockchainScanner.cpp:650) scanned from height #195969 to #195969
-WARN  - 19:46:10: (BDM_supportClasses.cpp:1898) running 10 zc parser threads
-WARN  - 19:46:10: (BDM_supportClasses.cpp:1898) running 15 zc parser threads
-WARN  - 19:46:10: (BDM_supportClasses.cpp:1898) running 20 zc parser threads
-WARN  - 19:46:10: (BDM_supportClasses.cpp:1898) running 25 zc parser threads
-WARN  - 19:46:10: (BDM_supportClasses.cpp:1898) running 30 zc parser threads
-WARN  - 19:46:10: (BDM_supportClasses.cpp:1898) running 35 zc parser threads
-INFO  - 19:53:57: (BDM_Server.cpp:1050) unregistered bdv: 4ba6700ae9e71bd3c3cc
-INFO  - 19:53:57: (BDM_Server.cpp:961) proceeding to shutdown
-ERROR - 19:54:00: (BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread
-INFO  - 19:54:00: (BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-ERROR - 19:54:00: (BDM_mainthread.cpp:287) caught exception in main thread: terminate

The other log file has a lot of private info I will need to edit. If it's important let me know and I'll do that.