Author

Topic: ArmoryDB doesn't scan blocks, no errors in log (Read 246 times)

legendary
Activity: 3766
Merit: 1364
Armory Developer
I guess it's ok as a temporary solution but still would like to know why armoryqt freezes and won't start armorydb on it's own.

https://github.com/goatpig/BitcoinArmory/blob/master/ArmoryQt.py#L1795

It runs this check on port 9001 instead of your custom one. Possibly the value hasn't been reflect in ArmoryQt.py cause it's hardcoded in ArmoryUtils.py and the compiler is that dumb?
full member
Activity: 175
Merit: 100
1) Check port 15000 isn't in use.
2) Check ArmoryQt is actually trying to connect to localhost:15000
3) Start ArmoryDB manually if you have to, give it the proper port.

1) Yes, did that using tcpview.

2) ArmoryQT never connects to 15000 even when running properly, only 8223.
At least that's what tcpview showed.

3) Tried this again and it works only if you start armorydb manually first then launch armoryqt.
I haven't tried any transactions yet but everything looks normal.
I guess it's ok as a temporary solution but still would like to know why armoryqt freezes and won't start armorydb on it's own.
Also I noticed that if you launch armoryqt first then start armorydb manually it won't connect to the db and tcpview fills up with system processes using port 9001.
newbie
Activity: 22
Merit: 6
I also get a fcgi error. Mine is a bit different.
Quote
-ERROR - 15:36:48: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte

Now I'll try with "rebuild".
Quote
$ armory
Gtk-Message: 15:41:01.203: Failed to load module "canberra-gtk-module"
/home/jbarcelo
(ERROR) ArmoryUtils.py:3735 - Unsupported language  specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:3126: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
No systemtrayicon available
(WARNING) SDM.py:402 - Spawning DB with command: ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/jbarcelo/.bitcoin/blocks" --satoshi-port=8333 --datadir="/home/jbarcelo/.armory/" --dbdir="/home/jbarcelo/.armory/databases" --rebuild
(ERROR) ArmoryQt.py:1198 - 5 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.
legendary
Activity: 3766
Merit: 1364
Armory Developer
1) Check port 15000 isn't in use.

2) Check ArmoryQt is actually trying to connect to localhost:15000

3) Start ArmoryDB manually if you have to, give it the proper port.
full member
Activity: 175
Merit: 100
Yes, I'm using windows 10 and nice trick! Modifying the AmoryUtils.py does work to change the port number to 15000 but armoryqt still freezes, won't start armorydb and I still get the same fcgi error in the rapidly growing armorycpplog.txt.

Code:
Log file opened at 16:23:20.000: D:\armory\armorycpplog.txt
-ERROR - 16:23:32.469: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
-ERROR - 16:23:32.485: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version

armorylog.txt
Code:
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1164 - C++ block utilities loaded successfully
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1281 -
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1282 -
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1283 -
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1284 - ************************************************************
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1285 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=D:\armory --dbdir=D:\armory\databases --satoshi-datadir=D:\bitcoin\blocks
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1286 - ************************************************************
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1287 - Loading Armory Engine:
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1288 -    Armory Version        : 0.96.5
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1289 -    Armory Build:         : 8730390989
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1290 -    PyBtcWallet  Version  : 1.35
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1291 - Detected Operating system: Windows
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1292 -    OS Variant            : 10-10.0.18362--Multiprocessor Free
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1293 -    User home-directory   : C:\Users\me\AppData\Roaming
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1294 -    Satoshi BTC directory : D:\bitcoin
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1295 -    Armory home dir       : D:\armory
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1296 - Detected System Specs    :
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1297 -    Total Available RAM   : 15.88 GB
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1298 -    CPU ID string         : Intel64 Family 6 Model 142 Stepping 9, GenuineIntel
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1299 -    Number of CPU cores   : 4 cores
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1300 -    System is 64-bit      : True
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1301 -    Preferred Encoding    : cp1252
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1302 -    Machine Arch          : amd64
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1303 -    Available HDD (ARM)   : 3340 GB
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1304 -    Available HDD (BTC)   : 3340 GB
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1305 -
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1306 - Network Name: Main Network
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1307 - Satoshi Port: 8333
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1308 - Do wlt check: True
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1309 - Named options/arguments to armoryengine.py:
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     force_segwit    : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     nettimeout      : 2
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     rescan          : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     force_fcgi      : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     ignoreAllZC     : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     rescanBalance   : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     disableModules  : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     port            : None
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     interport       : 8223
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     coverageOutputDir: None
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     forceWalletCheck: False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     regtest         : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     rebuild         : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     thread_count    : -1
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     datadir         : D:\armory
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     clearMempool    : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     offline         : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     armoryDBDir     : D:\armory\databases
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     armorydb_port   : 15000
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     satoshiPort     : DEFAULT
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     disableConfPermis: False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     useTorSettings  : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     netlog          : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     keypool         : 100
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     coverageInclude : None
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     forceOnline     : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     disableWalletCheck: False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     redownload      : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     rpcBindAddr     : 127.0.0.1
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     armorydb_ip     : 127.0.0.1
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     multisigFile    : DEFAULT
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     ram_usage       : -1
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     ignoreZC        : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     logDisable      : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     settingsPath    : D:\armory\ArmorySettings.txt
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     language        : en
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     db_type         : DB_FULL
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     doDebug         : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     enableDetSign   : True
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     mtdebug         : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     testnet         : False
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     rpcport         : DEFAULT
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     satoshiHome     : D:\bitcoin\blocks
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     satoshiRpcport  : DEFAULT
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     logFile         : D:\armory\ArmoryQt.exe.log.txt
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1311 -     verbosity       : None
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1312 - Other arguments:
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1315 - ************************************************************
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:1720 - C++ block utilities loaded successfully
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:3578 - Using settings file: D:\armory\ArmorySettings.txt
2020-07-31 16:23:20 (ERROR) -- ArmoryUtils.py:3735 - Unsupported language  specified. Defaulting to English (en)
2020-07-31 16:23:20 (INFO) -- ArmoryUtils.py:3738 - Using Language: en
2020-07-31 16:23:20 (INFO) -- BDM.pyc:353 - Using the asynchronous/multi-threaded BlockDataManager.
2020-07-31 16:23:20 (INFO) -- BDM.pyc:354 - Blockchain operations will happen in the background. 
2020-07-31 16:23:20 (INFO) -- BDM.pyc:355 - Devs: check TheBDM.getState() before asking for data.
2020-07-31 16:23:20 (INFO) -- BDM.pyc:356 - Registering addresses during rescans will queue them for
2020-07-31 16:23:20 (INFO) -- BDM.pyc:357 - inclusion after the current scan is completed.
2020-07-31 16:23:22 (INFO) -- ArmoryUtils.py:3578 - Using settings file: D:\armory\ArmorySettings.txt
2020-07-31 16:23:28 (INFO) -- ArmoryQt.py:2060 - loadWalletsAndSettings
2020-07-31 16:23:28 (INFO) -- ArmoryQt.py:2120 - Loading wallets...
2020-07-31 16:23:28 (INFO) -- ArmoryQt.py:2195 - Loading Multisig Lockboxes
2020-07-31 16:23:28 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:1513 - URL-register action: AskUser
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:1699 -    From: Expert
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:1707 -      To: Expert
2020-07-31 16:23:30 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2020-07-31 16:23:32 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1

Any ideas on what else could be tripping the fcgi error? The only thing that changed on my pc since the last successful run was windows updates.
legendary
Activity: 3766
Merit: 1364
Armory Developer
Well then there's a final trick, but it's worth trying. I'm going to guess you're on Windows, which is the only OS on which changing the Python code files is tricky.

As I said it's tricky but not impossible. Python code isn't compiled per se, it's interpreted. In the windows package, Armory bundles the Python interpreter along with the binary source for each python code file. This is so that Windows users can just run one executable. This executable starts the Python interpreter, and then points it to the Python code files in a zip archive: library.zip.

If you change a code in that library, it should be reflected in your setup. The idea is therefor to change hardcoded port in ArmoryUtils.py and replace that file in the code library zip archive. This would be a text file and not a binary file, so I'm not 100% sure that trick will work, but Python typically converts text files to binary files on the fly at import time so it should work.

You would need to change the port value at this line:

https://github.com/goatpig/BitcoinArmory/blob/master/armoryengine/ArmoryUtils.py#L88

Then copy the modified file in the zip archive (it's in the armoryengine folder), and delete the old file (ArmoryUtils.pyc). Your file is a .py (text), the file you're getting rid of is in binary (.pyc). Python should do the conversion for you next time your run Armory.
full member
Activity: 175
Merit: 100
yes sir, with or without quotes makes no difference.
legendary
Activity: 3766
Merit: 1364
Armory Developer
Have you tried putting the port in quotes?
full member
Activity: 175
Merit: 100
Thanks for the quick reply!

I get the same results and errors whether port is specified on cmd line or config files.

Code:
2020-07-30 14:02:02 (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 &'

It looks like the same "TypeError:" on line 1796 carcinogen is getting.


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:

Code:
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:

Code:
-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.

The problem with changing port number is only in armoryqt.exe as I can run armorydb.exe with a port number specified on the cmd line and it appears to work ok.
legendary
Activity: 3766
Merit: 1364
Armory Developer
Try setting the port through armoryqt.conf (for ArmoryQt) and armorydb.conf (for ArmoryDB)
full member
Activity: 175
Merit: 100

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:

Code:
-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.

I'm getting the same program freeze while starting Armory with the same error and rapidly growing armorycpplog.txt file.

Everything worked fine the last time I ran Armory about a month ago so I assume some windows update caused the issue.

Port 9001 is also being shown used by some unknown windows system process on my pc.

Also getting the same python refusing to read the string error when using the --armorydb-port= cmd line option.

Is there a work around for this or can it only be fixed with an Armory update?
legendary
Activity: 3766
Merit: 1364
Armory Developer
For some reason, python is refusing to read the port as a string.

https://github.com/goatpig/BitcoinArmory/blob/master/ArmoryQt.py#L1796

Forcing str() there may be of help.
newbie
Activity: 4
Merit: 1
Tried this, unfortunately the same result occurred.
legendary
Activity: 3766
Merit: 1364
Armory Developer
Then I run armoryqt.exe --armorydb-port=9002 --satoshi-datadir="F:\Bitcoin" and it fails to go online with the following log:

Sounds like python/swig shenanigans. Try

Code:
armoryqt.exe --armorydb-port="9002" --satoshi-datadir="F:\Bitcoin"
newbie
Activity: 4
Merit: 1
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:

Code:
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:

Code:
-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.
legendary
Activity: 3766
Merit: 1364
Armory Developer
Failed to talk to Core RPC, useful but not crucial. Are you running Core with --server=1?
newbie
Activity: 4
Merit: 1
OK, I discovered that the satoshi-datadir is actually Bitcoin\blocks\blocks for some reason. After setting this, ArmoryDB starts to parse but throws the following error every couple blocks:

Code:
-ERROR - 11:27:59.234: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:114) RPC connection test error: invalid object encapsulation

Is this an error to be concerned about?
newbie
Activity: 4
Merit: 1
I am running a synced full node and the latest 96.5 version of Armory, having deleted the old database files and performed a clean reinstall.

Originally I had a conflict on port 9001 which I believe has something to do with either Quickbooks networking or Intel drivers.

I then tried to run ArmoryDB using the following argument:

Code:
ArmoryDB.exe --fcgi-port=15000 --satoshi-datadir="F:\Bitcoin" --datadir="C:\Users\chris\AppData\Roaming\Armory"

Per the log, ArmoryDB stops doing anything on "Enabling zero-conf tracking" for hours.

Log below:

Code:
Log file opened at 10:33:55.000: C:\Users\chris\AppData\Roaming\Armory/dbLog.txt
-INFO  - 10:33:55.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 8 threads
-INFO  - 10:33:55.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO  - 10:33:55.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: F:\Bitcoin/blocks
-INFO  - 10:33:55.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: C:\Users\chris\AppData\Roaming\Armory/databases
-INFO  - 10:33:55.000: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 10:33:55.000: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port 15000
-INFO  - 10:33:55.079: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:947) Connected to Bitcoin node
-INFO  - 10:33:55.079: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:57) RPC connection established
-INFO  - 10:33:55.547: (e:\users\goat\code\armory3\cppforswig\blockdatamanagerconfig.cpp:919) waiting on node sync: 99.9999%
-INFO  - 10:33:56.657: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:425) Node is ready
-INFO  - 10:33:56.657: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 10:33:56.657: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-WARN  - 10:33:56.657: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:1241) No headers in DB yet!
-INFO  - 10:33:56.657: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 1 headers in db
-INFO  - 10:33:56.657: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO  - 10:33:56.657: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain
-INFO  - 10:33:56.657: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:370) Organized chain in 0s
-INFO  - 10:33:56.657: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:76) updated HEADERS db in 0s
-INFO  - 10:33:56.657: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 10:33:56.672: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1231) verifying txfilters integrity
-INFO  - 10:33:56.672: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1314) done checking txfilters
-INFO  - 10:33:56.672: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:1891) Enabling zero-conf tracking

I tried running armoryqt --armorydb-port=15000 --force-fcgi on top of the ArmoryDB but get "Armory failed to spawn the DB!" error.

I also tried running the same ArmoryQT command without ArmoryDB running, which produces the same result.

Any ideas?
Jump to: