Allow user to specify identity manually

[Catorpilor]

All the commands run as root

Run 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 for the node to set up.
Here are some logs

// this is ok during the initial setup
2019-04-17T04:23:09.801Z - info - Getting the identity
2019-04-17T04:23:09.802Z - info - Identity not provided, generating new one...
// call Contract and generate identity
.....
2019-04-17T04:14:04.119Z - info - OT Node started
2019-04-17T04:14:05.122Z - trace - Command cleanerCommand and ID fd591658-f151-4d1c-be2e-a30b4d238c4e started.
2019-04-17T04:14:05.137Z - trace - Command autoupdaterCommand and ID e17aeea7-5a01-47d6-9532-120524ad252c started.
2019-04-17T04:14:05.148Z - info - Checking for new node version
2019-04-17T04:14:05.336Z - trace - Version check: local version 2.0.54, remote version: 2.0.54
2019-04-17T04:14:05.339Z - info - No new version found
// cause we're in the inter-active mode, i press CTRL-C
^C2019-04-17 04:14:24,057 WARN received SIGINT indicating exit request
2019-04-17 04:14:24,058 INFO waiting for remote_syslog, otnode, arango, otnodelistener to die
2019-04-17 04:14:27,063 INFO waiting for remote_syslog, otnode, arango, otnodelistener to die
2019-04-17 04:14:28,266 INFO stopped: arango (exit status 0)
2019-04-17 04:14:29,269 INFO stopped: otnode (terminated by SIGTERM)
2019-04-17 04:14:29,272 INFO stopped: remote_syslog (terminated by SIGTERM)
2019-04-17 04:14:29,274 INFO stopped: otnodelistener (terminated by SIGTERM)

Then i run docker start otnode got the following errors issue 867

2019-04-17T04:14:52.538Z - 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-04-17T04:14:52.545Z - info - Notifying Bugsnag of exception...
Error: connect ECONNREFUSED 127.0.0.1:8529
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1174:14)
2019-04-17T04:14:52.550Z - error - Whoops, terminating with code: 1

docker restart otnode did not work then i ran docker rm otnode and the set up command again.
Here is a problem cause i've already made a contract and got my identity, so the second time i made a new contract and got the following errors:

2019-04-17T04:25:05.666Z - trace - Get profile by identity 
**my old identify**
2019-04-17T04:25:06.073Z - error - Unhandled Rejection:
Error: ERC725 profile not created for this node ID. My identity **new identify**, 
profile's node id: <node id>.
    at OTNode.bootstrap (/ot-node/init/ot-node.js:439:19)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:182:7)

Expected Behavior

When run 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 there should have a way for user to provide the identify, either by docker variables or some new fileds in the .origintrail_noderc file.

Specifications

• Version: v2.0.54
• Platform: ubuntu 18.04

[kipliklotrika]

Hi @Catorpilor,

You can reuse ERC 725 profile if you already have one. You just need to specify it in the docker command during container initiation. For example:

docker run -it --name=otnode -p 8900:8900 -p 5278:5278 -p 3000:3000
-v ~/.origintrail_noderc:/ot-node/.origintrail_noderc
-v ~/.identity.json:/ot-node/data/identity.json
-v ~/.erc725_identity.json:/ot-node/data/erc725_identity.json
quay.io/origintrail/otnode-mariner:release_mariner

The whole procedure is described here: http://docs.origintrail.io/en/latest/wallet-setup.html#network-identity

Please make sure you remember the network identity as well, since it is bound to the ERC 725 identity.

Regarding the Please make sure Arango server is up and running, it is the known issue.

Hope this helps.

[Catorpilor]

So what about my second contract? Is there any cancel contract function i can call?

[kipliklotrika]

It's yours, there's no back. You can use with other node.

[Catorpilor]

Is is OK to use the same operational wallet for multiple nodes? @kipliklotrika

[kipliklotrika]

In theory yes but in practice nodes will eventually ran into a problem with the transaction nonce. Meaning it's fair easy for a transaction to fail if other nodes signing their transactions at the same time.

[gdewitt23]

Is it okay to use the same wallet for operational and management?