• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

masternode start-missing started some MNs again and again

Solaso

Member
Hello! Please help me. Why my some mns started again and again?
All servers are same and made from one pattern, and other servers are work fine. All servers are synced latest 0.12.0.56 on servers and cold wallet.
All servers have a mn_watch script for restart, if not avaliable and work fine.


So, some MNs started again, for example:

14:40:32


cmd-request



masternode start-missing


14:40:32


cmd-reply



{
"overall" : "Successfully started 2 masternodes, failed to start 0, total 2",
"detail" : {
"status" : {
"alias" : "mn1",
"result" : "successful"
},
"status" : {
"alias" : "mn9",
"result" : "successful"
},

}
}
 
Go and resend the 1000 coins to the same address.... it will create a new tx_id and probably index.....wait 15 confirmations and restart again and report back if is stable now.
At least I had the same issues before and this helped always....

You can try to remove all dat files in your appdata except masternode.conf, wallet.dat and blockchain and restart them again, if not helped do the first steps....
 
Yeah there will be 2000 visible in the address in blockchain. You will have 1000 anyway but you will need to get the new tx id and change it in the masternode.conf before starting missing ;)
 
Yeah there will be 2000 visible in the address in blockchain. You will have 1000 anyway but you will need to get the new tx id and change it in the masternode.conf before starting missing ;)
Done, but all missing MNs are Could not allocate vin. I changed to 0 or 1 index number, then restarted, but not helped

13:53:44


cmd-request



masternode start-missing



13:53:44


cmd-reply



{
"overall" : "Successfully started 0 masternodes, failed to start ",
"detail" : {
"status" : {
"alias" : "mn1",
"result" : "failed",
"errorMessage" : "Could not allocate vin dff2e1fbf7322d594a30041ab2070fb796a98af7e53739d6e9e9785bd492607e:1 for masternode 188.227.74.28:9999"
},
"status" : {
"alias" : "mn9",
"result" : "failed",
"errorMessage" : "Could not allocate vin 4ee14dc1f36868f151dd183d39db9829a20e83419754debf9f5f7cff5d445b3a:0 for masternode 212.116.121.74:9999"
},

}
}
 
Has your client synced all? If you are in the state of syncing wait til the progress bar complete.

OR

If you moved the coin on the addresses of these nodes you need to update your config before start.

Check my PM.
 
Back
Top