search

synechron-finlabs / quorum-maker

Utility to create and monitor Quorum nodes
Apache License 2.0
196 stars 97 forks source link

Issue while connecting to an existing node #95

Open naveen-appoets opened 5 years ago

naveen-appoets commented 5 years ago

Incorrect Usage. invalid value "--rpc" for flag -raftjoinexisting: strconv.ParseInt: parsing "--rpc": invalid syntax

Followed by the below ones.

{"level":"info","msg":"Node Manager listening on :22004...","time":"2019-03-27T11:31:07Z"} rpc call eth_coinbase() on http://localhost:22000: Post http://localhost:22000: dial tcp 127.0.0.1:22000: connect: connection refused rpc call eth_coinbase() on http://localhost:22000: Post http://localhost:22000: dial tcp 127.0.0.1:22000: connect: connection refused rpc call eth_coinbase() on http://localhost:22000: Post http://localhost:22000: dial tcp 127.0.0.1:22000: connect: connection refused rpc call eth_coinbase() on http://localhost:22000: Post http://localhost:22000: dial tcp 127.0.0.1:22000: connect: connection refused

I get this issue while connecting to an existing node. Initially it worked fine, lot of nodes are infact attached to it already.

Joining a 6 node, I get this error. Not exactly sure why and I don't think its a firewall issue at the moment, I disabled all.

In the geth log, I found the geth command internally is passed as,

geth --verbosity 6 --datadir qdata --raft --nodiscover --networkid 61346 --raftjoinexisting --rpc --rpcaddr 0.0.0.0 --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,quorum,raft --emitcheckpoints --raftport 22003 --rpcport 22000 --port 22001 --nat extip:<ip here> invalid value "--rpc" for flag -raftjoinexisting: strconv.ParseInt: parsing "--rpc": invalid syntax

When in the working node, the geth log showed something like this,

geth --verbosity 6 --datadir qdata --raft --nodiscover --networkid 61346 --raftjoinexisting 2 --rpc --rpcaddr 0.0.0.0 --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,quorum,raft --emitcheckpoints --raftport 22003 --rpcport 22000 --port 22001 --nat extip:<ip here>

rjbanner commented 5 years ago

@naveen-appoets This would indicate that the raft id was not successfully passed in the failing nodes and hence they are unable to start up correctly. The raft id would have been returned to the potential joiners after performing the raft.addPeer command. The fact that the network id was returned correctly indicates that communication has taken place correctly. The second communication which sends the raft id and the Network Manager Contract address might have failed. Can you check the setup.conf of the failing joiners and check whether the CONTRACT_ADD property is blank or populated

sushant-at-nitor commented 4 years ago

Is this resolved? I am facing the same issue when I am trying to add a new node to the network. Can we try upgrading the QM and Quorum version? Do you guys have any docs for applying the upgrade to the live network, without taking it down?