Pages:
Author

Topic: ArmoryQt on Windows still broken with remote ArmoryDB on Ubuntu? - page 2. (Read 873 times)

legendary
Activity: 3766
Merit: 1364
Armory Developer
Code:
fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;
include        fastcgi_params;

Does the file with the fcgi_params exist?
member
Activity: 83
Merit: 10
Sorry to dredge this up from the past, but I've found questions relating to this with no real answers....

I'm trying to run ArmoryQt on win10-64, with ArmoryDB and bitcoind running on an Ubuntu VM -- Using armoryDB remotely is a new configuration for me, so I don't know if this issue is related to using 0.96.0.3-testing

ArmoryQt is running from the following command-line
Code:
@runas /savecred /user: "D:\Storage\\armory\program\ArmoryQt.exe --datadir=D:\Storage\\armory\data --armorydb-ip= --armorydb-port=9002"

ArmoryQt shows the splash screen, gets to 100%, then pops up "Errors occurred" with a reference to ArmoryQt.exe.log
I think the relevant bits from the logfile are:
Code:
2017-06-24 18:36:10 (INFO) -- ArmoryQt.py:1820 - startBitcoindIfNecessary
2017-06-24 18:36:10 (WARNING) -- ArmoryQt.py:1810 - DB is already running
2017-06-24 18:36:10 (INFO) -- ArmoryQt.py:1908 - Setting netmode: 1
2017-06-24 18:36:10 (ERROR) -- Traceback (most recent call last):
  File "ArmoryQt.py", line 5958, in
  File "ArmoryQt.py", line 679, in __init__
  File "ArmoryQt.py", line 5726, in startBlockchainProcessingInitialization
  File "ArmoryQt.py", line 5748, in completeBlockchainProcessingInitialization
  File "armoryengine\BDM.pyc", line 189, in instantiateBDV
TypeError: in method 'BlockDataViewer_getNewBDV', argument 1 of type 'string const &'

ArmoryDB is running with just the binary (I fished it out of the Ubuntu package because I don't want to install 500MB of dependencies for it), with the following command:
Code:
./ArmoryDB --satoshi-datadir="/data/bitcoind" --datadir="/data-ssd/armorydb"

ArmoryDB does not react at all -- no log entries when I launch ArmoryQt. It does appear to be fully synced up and ready to go.
Code:
logging in /data-ssd/armorydb/dbLog.txt
-INFO  - 19:04:17: (main.cpp:29) Running on 4 threads
-INFO  - 19:04:17: (main.cpp:30) Ram usage level: 4
-INFO  - 19:04:17: (BlockUtils.cpp:907) blkfile dir: /data/bitcoind/blocks
-INFO  - 19:04:17: (BlockUtils.cpp:908) lmdb dir: /data-ssd/armorydb/databases
-INFO  - 19:04:17: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 19:04:17: (BDM_Server.h:248) Listening on port 9001
-ERROR - 19:04:17: (nodeRPC.cpp:150) unexpected cookie file content
-ERROR - 19:04:17: (nodeRPC.cpp:150) unexpected cookie file content
-INFO  - 19:04:17: (BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 19:04:17: (BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 19:04:17: (DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 19:04:19: (DatabaseBuilder.cpp:208) Found 472811 headers in db
-INFO  - 19:04:20: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 19:04:21: (DatabaseBuilder.cpp:268) parsed block file #914
-INFO  - 19:04:21: (DatabaseBuilder.cpp:268) parsed block file #915
-DEBUG - 19:04:21: (Blockchain.cpp:242) Organizing chain
-INFO  - 19:04:21: (DatabaseBuilder.cpp:56) updated HEADERS db in 1.01823s
-INFO  - 19:04:21: (BDM_supportClasses.cpp:1841) Enabling zero-conf tracking
-WARN  - 19:04:25: (BDM_supportClasses.cpp:1898) running 10 zc parser threads
-WARN  - 19:04:25: (BDM_supportClasses.cpp:1898) running 15 zc parser threads
-WARN  - 19:04:25: (BDM_supportClasses.cpp:1898) running 20 zc parser threads
-WARN  - 19:05:17: (BDM_supportClasses.cpp:1898) running 25 zc parser threads
-WARN  - 19:05:17: (BDM_supportClasses.cpp:1898) running 30 zc parser threads

nginx is running on ubuntu, with the following config:
Code:
user www-data;
worker_processes auto;
pid /run/nginx.pid;

events {
    worker_connections  1024;
}

http {
    keepalive_timeout  0;

    server {
        listen       9002;
        server_name  localhost;

        location / {
            root           /;
            fastcgi_pass   127.0.0.1:9001;
            fastcgi_index  /;
            fastcgi_buffering on;
            fastcgi_buffer_size 4k;
            fastcgi_buffers 16 4k;
            fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;
            include        fastcgi_params;
        }
    }
}

I can connect to http://:9002/ and I get a hex value returned

Sorry for the long post, is there any more debug information I can get you, and do you have any idea what's going wrong with this setup?



Pages:
Jump to: