Quote from: bible_pay on December 17, 2017, 03:28:24 PM

Quote from: 616westwarmoth on December 17, 2017, 02:26:25 PM

When looking at the masternode winners output from debug, it shows

Code:

"21551": "B547NvFM2TUeCKxEGcxCxpt8as42pyS4po:10",
  "21552": "BDkocGarpfSBMuT15p9dQzsAfNqsgb2UHh:10",
  "21553": "B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ:9",
  "21554": "B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ:9",
  "21555": "B8se8LxzDo9AKmSB9fnY38gbc3ubedRZxJ:10",
  "21556": "B8se8LxzDo9AKmSB9fnY38gbc3ubedRZxJ:9",
  "21557": "BSrFn8zpC48AykVANWcjVEve5tzn8NQNRE:9",
  "21558": "BSrFn8zpC48AykVANWcjVEve5tzn8NQNRE:10",
  "21559": "BCb8B85R4mpuiy62Sbs9W4Xv2w5CVEJ5TS:10",

Noticed block 21553 and 554 both went to the same payee, same with the 55/56 and 57/58. Only one MN in the list has each of these addresses. Am I misreading that, or is there something more to understand?

That should be OK if one controller has multiple masternodes; lets verify 100 payments after we get back up.

So after you upgrade your linux box, the last few blocks in the chain are bad because the tithe was paid at that height.

Go ahead and click OK to let it rebuild the block index.

Alex and I are working on this now to ensure we resync up to 21551. This upgrade only talks to other nodes of the same protocol version, hence the reason it is not going smoothly.

We are working it out now.

Please wait two more hours for the windows update.

ROb , how long should it take to rebuild the block DB ?

I've been running it for more than an hour with no luck . stopped it .

can you post an IP of the node with a healthy rebuilt DB so we can force connection and resync ?