Armory states not to be online and does nothing to change this

[HCP]

Based on the log files provided, I believe the issue is related to the fact that the OP has a so-called "portable" install of Bitcoin Core... and Armory is simply unable to find it (not in default "Program Files" location etc.)

I've only been able to replicate this exact error ("BitcoindError: bitcoind not found") by having Armory set to "Let Armory run Bitcoin Core/bitcoind in the background"... and not having the correct folder locations specified:



If that setting isn't checked, I just get: "2018-11-14 11:18:19 (ERROR) -- ArmoryQt.py:1878 - Bitcoin installation setting is a non-existent directory"


So, my advice would be to tick the box and put in the correct paths:

"Bitcoin Install Dir" = Path to where your Bitcoin Core "Portable" dir is... (NOTE: Armory is expecting bitcoind.exe to be in a subfolder named "daemon")
"Bitcoin Home Dir" = Path to the Bitcoin "datadir" (this folder will contain the "blocks" subfolder)


ie. if you have your portable Bitcoin extracted to "E:\portableBitcoin" then your "Bitcoin Install Dir" should have a structure like this:

E:\portableBitcoin (should contain bitcoin-qt.exe)
E:\portableBitcoin\daemon (should contain bitcoind.exe and bitcoin-cli.exe)


If you plan on starting Bitcoin Core yourself (because you want to use the GUI for something)... you can actually have the box unticked and it should work OK, IF you have the correct paths showing in the 2 boxes (ie. "open settings -> tick box -> enter correct paths -> save -> re-open settings -> untick box -> save")

[DrakonX]

Damn, it is the correct version, it's running and it's synced and it doesn't work anyway. The log obviously doesn't schon the correct status.

Thank you, HCP, for your detailed remarks. I did all the way you described it, without success.

Here it is what it looks like right now:

[HCP]

Can you post the log file now that it is setup like that?

Note: I forgot to mention that there is a priority to the "path" settings... I cannot seem to find the exact reference where goatpig mentioned it previously (and it doesn't seem to say in the "pathing" docs)... But it's possible that if you have one path specified in .conf and a different path specified in the GUI settings... Then Armory may not actually be using the path you think it is.

So, maybe try leaving those GUI settings and remove your .conf file... Delete the armorylog.txt and then try running it again.

If it still isn't working... post the new log file

[DrakonX]

It's working, now. Seems as I'd not have been patient enough during startup. Just had to wait a few moments untill it starts syncing (Armory syncing, not Core syncing).

I use the custom paths of "Bitcoin Install Dir" and "Bitcoin Home Dir" and it works.

Question: Where exactly is Armory building its database now?

[Carlton Banks]

Question: Where exactly is Armory building its database now?

\Armory_home_dir\databases

If you didn't specify Armory home directory, it will use the default directory on your platform

Armory uses ~ 1GB for the databases on mainnet bitcoin.

[DrakonX]

Unfortunatly, the program stops or seems to stuck at 20% while syncing. Don't know why. Here is the log: https://pastebin.com/jypTD4QY

Do I just have to wait? The disc symbol also stops rotating.

[Carlton Banks]

do you have sufficient disk space available for the databases?

[HCP]

Question: Where exactly is Armory building its database now?

According to the log file: C:\Users\Andreas\AppData\Roaming\Armory\databases

As for why it is stopping... It's possible, as Carlton suggested, there is not enough Disk space (it does mention 0GB space on BTC drive in the log??!?)... Or it might be that ArmoryDB is encountering an error.

Check dbLog.txt and/or post the contents

[DrakonX]

There ars still a lot of GB left on the disk. The demanded log file: https://pastebin.com/TBTF92QN

[HCP]

Nothing very obvious there unfortunately...

Do I just have to wait? The disc symbol also stops rotating.

How long did you leave it for before you shut it down? Sometimes Armory can appear to be "frozen" when it is in fact doing something in the background... If it was only a minute or two, then it might be that you were just a bit quick to pull the trigger

However, if you waited like 30-60 minutes and saw no progress then that would be indicative of a serious problem.