Quote from: achow101 on February 07, 2017, 10:15:55 PM

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