Mining stops when 2nd node is down

+1 vote
Setup: two nodes on the same host
Chain params: requires peers is false and mining diversity is 0.
    "mining-diversity" : 0.00000000,
    "mining-requires-peers" : false,

I confirmed the other node appears on the peer info list of each node and both nodes have permissions to mine. When both nodes are running, i see blocks being mined at the rate of one every 15 seconds. When i stop one of the nodes (say the 2nd node), i see the 1st node stops mining. I see the following messages in the log file.

2016-07-26 09:33:40 connect() to [::1]:8473 failed after select(): Connection refused (111)
2016-07-26 09:33:41 connect() to [::1]:8473 failed after select(): Connection refused (111)
2016-07-26 09:33:42 connect() to [::1]:8473 failed after select(): Connection refused (111)
2016-07-26 09:33:43 connect() to [::1]:8473 failed after select(): Connection refused (111)
asked Jul 26, 2016 by Romit K
Thanks for reporting this, which version are you using?
MultiChain Core Daemon build 1.0 alpha 22 protocol 10005

1 Answer

0 votes
Thank you for reporting this.

We've already fixed it and the fix will appear in alpha 23.

In the meantime you can set small non-zero value to mining-diversity:

mining-diversity = 0.000001
answered Jul 26, 2016 by Michael
Thank you Mike. I'll give your suggestion a try
...