Ninjastic
Search content
Sort by
Showing 4 of 4 results by carcinogen
Post
Topic
Board Armory
Re: ArmoryDB doesn't scan blocks, no errors in log
by
carcinogen
on 14/07/2020, 16:46:43 UTC
Tried this, unfortunately the same result occurred.
Post
Topic
Board Armory
Merits 1 from 1 user
Re: ArmoryDB doesn't scan blocks, no errors in log
by
carcinogen
on 13/07/2020, 21:32:34 UTC
⭐ Merited by nc50lc (1)
Quote from: goatpig on July 09, 2020, 08:46:21 PM
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.
Post
Topic
Board Armory
Re: ArmoryDB doesn't scan blocks, no errors in log
by
carcinogen
on 09/07/2020, 15:29:20 UTC
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?
Post
Topic
Board Armory
Topic OP
ArmoryDB doesn't scan blocks, no errors in log
by
carcinogen
on 09/07/2020, 14:41:37 UTC
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?