Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting dashcore-node to dashd-docker #56

Open
stxphxn opened this issue Mar 17, 2019 · 4 comments
Open

Connecting dashcore-node to dashd-docker #56

stxphxn opened this issue Mar 17, 2019 · 4 comments

Comments

@stxphxn
Copy link

stxphxn commented Mar 17, 2019

Hi,

I'm trying to connect dashcore to a Docker container running dashd, but when I start dash-core node my console is spammed with these messages.

2019-03-14T07:43:44.719Z] info: Using network: testnet
[2019-03-14T07:43:44.719Z] info: Starting dashd
[2019-03-14T07:43:44.809Z] info: Dash Daemon Ready
[2019-03-14T07:43:44.810Z] info: Starting web
[2019-03-14T07:43:44.825Z] info: Starting @dashevo/insight-api
[2019-03-14T07:43:44.825Z] info: Starting @dashevo/insight-ui
[2019-03-14T07:43:44.826Z] info: Dashcore Node ready
[2019-03-14T07:43:45.257Z] warn: ZMQ connection delay: tcp://127.0.0.1:28332
[2019-03-14T07:43:45.257Z] info: ZMQ connected to: tcp://127.0.0.1:28332
[2019-03-14T07:43:45.257Z] warn: ZMQ disconnect: tcp://127.0.0.1:28332
[2019-03-14T07:43:45.257Z] warn: ZMQ connection delay: tcp://127.0.0.1:28332
[2019-03-14T07:43:45.257Z] info: ZMQ connected to: tcp://127.0.0.1:28332
[2019-03-14T07:43:45.258Z] warn: ZMQ disconnect: tcp://127.0.0.1:28332
[2019-03-14T07:43:45.258Z] warn: ZMQ connection delay: tcp://127.0.0.1:28332
[2019-03-14T07:43:45.258Z] info: ZMQ connected to: tcp://127.0.0.1:28332
[2019-03-14T07:43:45.258Z] warn: ZMQ disconnect: tcp://127.0.0.1:28332
[2019-03-14T07:43:45.258Z] warn: ZMQ connection delay: tcp://127.0.0.1:28332
[2019-03-14T07:43:45.258Z] info: ZMQ connected to: tcp://127.0.0.1:28332
[2019-03-14T07:43:45.258Z] warn: ZMQ disconnect: tcp://127.0.0.1:28332

Here is my dash.conf

testnet=1
server=1
whitelist=127.0.0.1
txindex=1
addressindex=1
timestampindex=1
spentindex=1
zmqpubrawtx=tcp://127.0.0.1:28332
zmqpubhashblock=tcp://127.0.0.1:28332
rpcuser=dash
rpcpassword=rpcpassword
rpcallowip=127.0.0.1
uacomment=dashcore

and my dashcore-node.json

{
  "network": "testnet",
  "port": 3001,
  "services": [
    "@dashevo/insight-api",
    "@dashevo/insight-ui",
    "dashd",
    "web"
  ],
  "servicesConfig": {
    "dashd": {
       "connect": [{
        "rpchost": "127.0.0.1",
        "rpcport": 19998,
        "rpcuser": "dash",
        "rpcpassword": "rpcpassword",
        "zmqpubrawtx": "tcp://127.0.0.1:28332",
	"zmqpubhashblock": "tcp://127.0.0.1:28332"
      }]
    },
"@dashevo/insight-api": {
      "disableRateLimiter": true
    }
  }
}

Any help to get it working would be greatly appreciated.

@antouhou
Copy link
Collaborator

Hi @stxphxn! As far as I can tell, something wrong with the zmq connection. Does docker container with dashd use the same port as zmq in the config? Is this the only problem, API endpoints working as expected?

@stxphxn
Copy link
Author

stxphxn commented Mar 20, 2019

Yes, they're both using the same port. Is it possible that zmqpubrawtx and zmqpubhashblock need to run on separate ports?
The insight api endpoints don't work, but I can make RPC calls to the dash node running in docker.

@antouhou
Copy link
Collaborator

@stxphxn it's fine that the run on the same ports. My best guess would be that something isn't ok with the docker network configuration

@CryptoTeller
Copy link

I am also having this problem ZMQ connection delay anyone know what causes this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants