1

I am setting up a quorum network with Quorum-maker, which uses Geth. It is running at the moment, with three alive nodes. However, earlier I had attempted to create two other nodes, which failed. I have since killed them off.

Now, the master node is still trying to connect to them multiple times per second. This creates a lot of logs. These logs are in the gethLogs directory, which is why I believe this is a geth issue rather than quorum specific.

INFO [06-20|04:45:34.146] peer is currently unreachable peer id=4
2019-06-20 04:45:34.146757 I | rafthttp: peer 5 became active
2019-06-20 04:45:34.170051 E | rafthttp: failed to find member 1 in cluster 1000
2019-06-20 04:45:34.170210 E | rafthttp: failed to dial 5 on stream MsgApp v2 (peer 5 failed to find local node 1)
2019-06-20 04:45:34.170227 I | rafthttp: peer 5 became inactive
2019-06-20 04:45:34.170770 E | rafthttp: failed to find member 1 in cluster 1000
INFO [06-20|04:45:34.246] peer is currently unreachable            peer id=4
2019-06-20 04:45:34.246934 I | rafthttp: peer 5 became active
2019-06-20 04:45:34.270846 E | rafthttp: failed to find member 1 in cluster 1000
2019-06-20 04:45:34.271017 E | rafthttp: failed to dial 5 on stream MsgApp v2 (peer 5 failed to find local node 1)
2019-06-20 04:45:34.271034 I | rafthttp: peer 5 became inactive
2019-06-20 04:45:34.271437 E | rafthttp: failed to find member 1 in cluster 1000
INFO [06-20|04:45:34.346] peer is currently unreachable            peer id=4
2019-06-20 04:45:34.347058 I | rafthttp: peer 5 became active
2019-06-20 04:45:34.371589 E | rafthttp: failed to find member 1 in cluster 1000
2019-06-20 04:45:34.371746 E | rafthttp: failed to dial 5 on stream MsgApp v2 (peer 5 failed to find local node 1)
2019-06-20 04:45:34.371763 I | rafthttp: peer 5 became inactive
2019-06-20 04:45:34.372624 E | rafthttp: failed to find member 1 in cluster 1000
INFO [06-20|04:45:34.446] peer is currently unreachable            peer id=4
2019-06-20 04:45:34.447434 I | rafthttp: peer 5 became active
2019-06-20 04:45:34.472487 E | rafthttp: failed to find member 1 in cluster 1000
2019-06-20 04:45:34.472664 E | rafthttp: failed to dial 5 on stream MsgApp v2 (peer 5 failed to find local node 1)
2019-06-20 04:45:34.472680 I | rafthttp: peer 5 became inactive
2019-06-20 04:45:34.473471 E | rafthttp: failed to find member 1 in cluster 1000

The message itself makes perfect sense, these two nodes (4 & 5) don't exist anymore, hence it makes sense that geth can't connect. What I am looking for is a way to get Geth to stop trying to connect to these nodes. Ideally I want to delete them from the master node entirely. At the very least I want geth to stop logging about it.

1

You need to remove the stale nodes from Raft.

Instructions on how to do this can be found in the Quorum docs.

  • Hm, it says "attach to a JS console and issue raft.removePeer(raftId)", but doesn't explain what that means. How do I get this JS console with raft? – Max Binnewies Jun 21 at 2:23
  • You need to attach to the geth JS console to issue commands like raft.removePeer. That's done using geth attach, but you'll need a further parameter to specify the http address or the IPC file. Take a look in the Ethereum docs if you need further info on that - it's standard Ethereum. – Satpal Sandhu Jun 21 at 9:03
  • geth console is a wrapper around JSON-RPC methods geth node exposes via the rpcapi, wsapi, or ipc. You may also curl the API directly or use our JS library that offers raft API in the extensions: github.com/jpmorganchase/quorum.js – fixanoid Jun 21 at 13:16
  • @Satpal Sandhu: I'm afraid that still doesn't help. How do I get a "JS console"? geth attach just gets me the normal go terminal and raft doesn't work there. – Max Binnewies Jun 26 at 1:39
  • @fixanoid quorum-js seems to be broken, complains "TypeError: web3.extend is not a function" – Max Binnewies Jun 26 at 1:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.