connect ECONNREFUSED 127.0.0.1:8529

[PhuongThaoNguyen]

Expected Behavior

run OTnode in testnet network

Actual Behavior

Steps to Reproduce the Problem

2019-03-07T07:44:59.895Z - error - Please make sure Arango server is up and running
{ Error: connect ECONNREFUSED 127.0.0.1:8529
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1174:14)
errno: 'ECONNREFUSED',
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 8529,
response: undefined }
2019-03-07T07:44:59.898Z - info - Notifying Bugsnag of exception...

Specifications

• Version:
• Platform:

[PhuongThaoNguyen]

[user01010111]

This was happening to me as well, however (for me, at least) this was caused by running docker via "sudo".

To get this to work you need to run as root, so "sudo su" to move to root, then run your commands from there.

I'd recommend you:

sudo su
docker container rm otnode
docker run -it --name=otnode -p 8900:8900 -p 5278:5278 -p 3000:3000 -v /root/.origintrail_noderc:/ot-node/.origintrail_noderc quay.io/origintrail/otnode-mariner:release_mariner

Note the "docker run" command above has an absolute path, not the "~/.origintrail_noderc" path which I think is what was breaking it when run via sudo.

Also, your screenshot exposes your wallet address, your houston password and your public IP address. I would highly recommend you destroy the wallet and change your identity so these items are redacted correctly.

[djordjekovac]

This issue is being closed as inactive due to the date of the last activity on it. If you believe this is still a problem, please create a new issue and confirm that it is reproducible in the current ot-node release version.

We are working towards closing open issues that meet specific criteria and ask you to create a new one for those that that are truly bugs in current release. We'll be monitoring those issues so that they are properly managed.

Thank you,
OriginTrail Team