How do we find out why the node is not synchronizing?

+2 votes

abcoin: getinfo
{"method":"getinfo","params":[],"id":1,"chain_name":"abcoin"}

{
    "version" : "1.0 alpha 27",
    "protocolversion" : 10006,
    "chainname" : "abcoin",
    "description" : "MultiChain abcoin",
    "protocol" : "multichain",
    "port" : 8333,
    "setupblocks" : 60,
    "nodeaddress" : "abcoin@10.0.0.4:8333",
    "burnaddress" : "1XXXXXXWrpXXXXXXdzXXXXXXQiXXXXXXXWMNm3",
    "incomingpaused" : false,
    "miningpaused" : false,
    "walletversion" : 60000,
    "balance" : 235551.00000000,
    "walletdbversion" : 2,
    "reindex" : false,
    "blocks" : 649294,
    "timeoffset" : 0,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 0.00001526,
    "testnet" : false,
    "keypoololdest" : 1483196349,
    "keypoolsize" : 2,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00000000,
    "errors" : ""
}
abcoin: getpeerinfo
{"method":"getpeerinfo","params":[],"id":1,"chain_name":"abcoin"}

[
    {
        "id" : 26,
        "addr" : "52.175.220.130:8333",
        "addrlocal" : "52.175.220.130:36944",
        "services" : "0000000000000001",
        "lastsend" : 1483670522,
        "lastrecv" : 1483670522,
        "bytessent" : 1228861,
        "bytesrecv" : 1232053,
        "conntime" : 1483506536,
        "pingtime" : 0.00193300,
        "pingwait" : 7.86089500,
        "version" : 70002,
        "subver" : "/MultiChain:0.1.0.7/",
        "handshakelocal" : null,
        "handshake" : null,
        "inbound" : false,
        "startingheight" : 631340,
        "banscore" : 0,
        "synced_headers" : 649295,
        "synced_blocks" : 649295,
        "inflight" : [
        ],
        "whitelisted" : false
    },
    {
        "id" : 27,
        "addr" : "52.175.220.130:36944",
        "addrlocal" : "52.175.220.130:8333",
        "services" : "0000000000000001",
        "lastsend" : 1483670522,
        "lastrecv" : 1483670522,
        "bytessent" : 1232053,
        "bytesrecv" : 1228861,
        "conntime" : 1483506535,
        "pingtime" : 0.00188600,
        "pingwait" : 7.86056700,
        "version" : 70002,
        "subver" : "/MultiChain:0.1.0.7/",
        "handshakelocal" : null,
        "handshake" : null,
        "inbound" : true,
        "startingheight" : 631340,
        "banscore" : 0,
        "synced_headers" : 649295,
        "synced_blocks" : -1,
        "inflight" : [
        ],
        "whitelisted" : false
    },
    {
        "id" : 361,
        "addr" : "13.69.13.151:45820",
        "addrlocal" : "52.175.220.130:8333",
        "services" : "0000000000000001",
        "lastsend" : 1483670522,
        "lastrecv" : 1483670522,
        "bytessent" : 669434856,
        "bytesrecv" : 8726221,
        "conntime" : 1483632201,
        "pingtime" : 0.19824800,
        "version" : 70002,
        "subver" : "/MultiChain:0.1.0.7/",
        "handshakelocal" : null,
        "handshake" : null,
        "inbound" : true,
        "startingheight" : 645519,
        "banscore" : 0,
        "synced_headers" : 649510,
        "synced_blocks" : -1,
        "inflight" : [
        ],
        "whitelisted" : false
    }
]
 

 

After i reboot the node, I always use the following command to re-connect with the blockchain network

multichaind abcoin -daemon

Then i will see fork situation and it will never recover, when i use the following command, it seems to correct the fork.

multichaind abcoin@111.222.333.444:8333 -daemon

Why(sometimes) the node will not refer to the peerlist to seek the best block node for synchronization?

asked Jan 5, 2017 by chunhui323
edited Jan 6, 2017 by chunhui323

1 Answer

+2 votes

If you're seeing a fork, it will be because peers are not connected to each other as they should be. Perhaps the peers are changing IP addresses over time, in which case one node may not be able to find another? In general you can also use the addnode command to manage this while the node is running.

answered Jan 6, 2017 by MultiChain
...