Mrsuld
Mrsuld
Sep 9, 2018 · 1 min read

Hello, Troy McConadhy. Now I Redeploy BigchainDB 2.0.0b5 (tendermint 0.22.8).It’s facing the same problem.

Some of the tendermint log:

Successful handshake with peer module=p2p peer=192.168.200.42:54542 peerNodeInfo=”NodeInfo{id: cb7c1ba024721f8036a4ea6d2f3b2ad0b9c73bd7, moniker: node42, network: test-chain-PRlgMm [listen 192.168.100.42:26656], version: 0.22.8–40d6dc2e ([amino_version=0.10.1 p2p_version=0.5.0 consensus_version=v1/0.2.2 rpc_version=0.7.0/3 tx_index=on rpc_addr=tcp://0.0.0.0:26657])}”

Actually I add information to conifg.toml

persistent_peers=”……@192.168.200.42:26656,……@192.168.200.43:26656,……@192.168.200.44:26656,……@192.168.200.45:26656,

E[09–07|12:02:01.691] Dialing failed module=p2p addr=d9dee4a995121098b7cad112dab3bd8c59c39f9e@192.168.200.44:26656 err=”Error{dial tcp 192.168.200.44:26656: connect: connection refused}” attempts=0

E[09–07|12:02:01.691] Dialing failed module=p2p addr=578f1f0c6f3eeda60a9ea364b9f1e3c2625b36f7@192.168.200.45:26656 err=”Error{dial tcp 192.168.200.45:26656: connect: connection refused}” attempts=0

E[09–07|12:02:01.693] Dialing failed module=p2p addr=cb7c1ba024721f8036a4ea6d2f3b2ad0b9c73bd7@192.168.200.42:26656 err=”Duplicate peer ID cb7c1ba024721f8036a4ea6d2f3b2ad0b9c73bd7" attempts=0

E[09–07|12:02:01.694] Dialing failed module=p2p addr=85489d5433929259f43fc91497627beadde0858f@192.168.100.42:26656 err=”Failed to authenticate peer. Dialed 85489d5433929259f43fc91497627beadde0858f@192.168.100.42:26656, but got peer with ID cb7c1ba024721f8036a4ea6d2f3b2ad0b9c73bd7" attempts=0

……

Error dialing peer module=p2p err=”Error{dial tcp 192.168.200.45:26656: connect: connection refused}”

In addition,I can enter “curl -s 192.168.200.42:26657/net_info” to see the nodes’ information.

I guess the network is in conflict.There are two Network card on the servers. If I can set the listening address, the problem would be solved. Where can I set it?

    Mrsuld

    Written by

    Mrsuld