Failed to talk to Core RPC, useful but not crucial. Are you running Core with --server=1?
I added this to the config, and the RPC error went away.
IN the meantime, I deleted and redownloaded the entire blockchain with the correct pathing and cannot get ArmoryQt to play nice with ArmoryDB.
The problem stems from my Windows 10 installation which already has an Intel service listening on 9001.
I initialize armorydb.exe --fcgi-port=9002 --satoshi-datadir="F:\Bitcoin" and it appears to sync up properly.
Then I run armoryqt.exe --armorydb-port=9002 --satoshi-datadir="F:\Bitcoin" and it fails to go online with the following log:
2020-07-13 17:24:54 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1513 - URL-register action: AskUser
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:566 - Usermode: Advanced
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1699 - From: Advanced
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1707 - To: Advanced
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2020-07-13 17:24:56 (ERROR) -- ArmoryQt.py:1830 - Failed to start Armory database: in method 'BlockDataManagerConfig_hasLocalDB', argument 2 of type 'string const &'
Traceback (most recent call last):
File "ArmoryQt.py", line 1796, in startArmoryDBIfNecessary
TypeError: in method 'BlockDataManagerConfig_hasLocalDB', argument 2 of type 'string const &'
2020-07-13 17:24:56 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 0
2020-07-13 17:24:58 (INFO) -- ArmoryQt.py:5477 - BDM is safe for clean shutdown
2020-07-13 17:24:58 (INFO) -- SDM.pyc:465 - Called stopBitcoind
2020-07-13 17:24:58 (INFO) -- SDM.pyc:471 - ...but bitcoind is not running, to be able to stop
2020-07-13 17:24:58 (INFO) -- ArmoryQt.py:5490 - Attempting to close the main window!
I have also tried supplying "F:\Bitcoin\blocks" as the satoshi datadir with the same result.
I have also attempted to run Armory by itself without arguments so that it spawns the DB, but the program simply freezes and writes infinitely to armorycpplog.txt the following error:
-ERROR - 17:31:11.625: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
I assume this has something to do with port 9001 being unavailable because no such error appears when the term --armorydb-port=9002 is supplied.