Block Count not increasing when Main Node is stopped

+2 votes
I setup as following

1 main node

3 x miner node with mine permissions.

They all working just fine and the sync perfectly, i also can sendtoaddress just fine, miner also getting the mining fees.

when i try to stop the main node, the block simply not increasing anymore. may I know why?

as soon as i start the main node, of course, everything starts to work again. Is this how MultiChain work?



    "chain-protocol" : "multichain",
    "chain-description" : "MultiChain ZZZcoin",
    "root-stream-name" : "root",
    "root-stream-open" : true,
    "chain-is-testnet" : false,
    "target-block-time" : 15,
    "maximum-block-size" : 1000000,
    "default-network-port" : 9717,
    "default-rpc-port" : 9716,
    "anyone-can-connect" : true,
    "anyone-can-send" : true,
    "anyone-can-receive" : true,
    "anyone-can-create" : false,
    "anyone-can-issue" : false,
    "anyone-can-mine" : false,
    "anyone-can-activate" : false,
    "anyone-can-admin" : false,
    "allow-p2sh-outputs" : true,
    "allow-multisig-outputs" : true,
    "setup-first-blocks" : 60,
    "mining-diversity" : 0.30000000,
    "admin-consensus-admin" : 0.50000000,
    "admin-consensus-activate" : 0.50000000,
    "admin-consensus-mine" : 0.50000000,
    "admin-consensus-create" : 0.00000000,
    "admin-consensus-issue" : 0.00000000,
    "mining-requires-peers" : true,
    "first-block-reward" : -1,
    "initial-block-reward" : 9999999990,
    "reward-halving-interval" : 52560000,
    "reward-spendable-delay" : 40,
    "minimum-per-output" : 0,
    "maximum-per-output" : 100000000000000,
    "minimum-relay-fee" : 0,
    "native-currency-multiple" : 100000000,
    "skip-pow-check" : false,
    "pow-minimum-bits" : 16,
    "target-adjust-freq" : -1,
    "allow-min-difficulty-blocks" : false,
    "only-accept-std-txs" : true,
    "max-std-tx-size" : 100000,
    "max-std-op-returns-count" : 10,
    "max-std-op-return-size" : 4096,
    "max-std-op-drops-count" : 5,
    "max-std-element-size" : 600,
    "chain-name" : "ZZZcoin",
    "protocol-version" : 10006,
asked Oct 8, 2016 by chunhui323

1 Answer

+1 vote
Best answer

First please check if the nodes are connected to each other using getpeerinfo.

Then check that each node has an address in its wallet with mining permissions (getaddresses + listpermissions mine). If you ever used importaddress ensure you don't include watch-only addresses in this check.

Finally please confirm you are not using wallet encryption on any of the mining nodes.

You can also check who mined the last 10 blocks using getblock [block-number] and looking in the miner field. You should see variation in that field across all the nodes.

Please let us know what you find and we'll proceed from there.

answered Oct 10, 2016 by MultiChain
selected Mar 5, 2017 by chunhui323
Thanks You MC,

It seems that the type of VM that I have created previously have will not allow me to ping each other, that probably why the Multichain deployed seems not working.

The issue seems to be resolved now.

A few mistakes that I made as listed below.
1) mining-diversity set to 0 (Not sure why this cause each node to mine on its own) when i do a comparison between each node using getblock 123, each node is having its own different "miner" for the block.

to fix this, i set it mining-diversity= 0.00001

2) another issue with the few Ubuntu VMs that I created cant ping each other
I tried to create new VM using the template here

with these 2 changes, my genesis node can go offline and the blockchain still running fine,
chunhui323, The azure link is broken..
It would be nice to see the answer because, we have 1 resolve and the 2nd answer is broken?

The 2 answers to this are.
mining-diversity= 0.00001
Make sure it can be pinged :-)

That's what I derived.

P. S.  your VM might have an extension pack that needs to be installed for functionality to become available.

or maybe someone could elaborate.
and finish his possible last thing mentioned as a solution?