My many masternodes dont win not onсe
- Thread starter Solaso
- Start date
Now I am again "masternode start-disabled" and see many MNs started again, why? So I cannot win never
{
"overall" : "Successfully started 36 masternodes, failed to start 0, total 5",
"detail" : {
"status" : {
"alias" : "mn1",
"result" : "successful"
},
"status" : {
"alias" : "mn2",
"result" : "successful"
},
"status" : {
"alias" : "mn3",
"result" : "successful"
},
"status" : {
"alias" : "mn4",
"result" : "successful"
},
"status" : {
"alias" : "mn5",
"result" : "successful"
},
}
}
{
"overall" : "Successfully started 36 masternodes, failed to start 0, total 5",
"detail" : {
"status" : {
"alias" : "mn1",
"result" : "successful"
},
"status" : {
"alias" : "mn2",
"result" : "successful"
},
"status" : {
"alias" : "mn3",
"result" : "successful"
},
"status" : {
"alias" : "mn4",
"result" : "successful"
},
"status" : {
"alias" : "mn5",
"result" : "successful"
},
}
}
Last edited by a moderator:
thelazier
Active member
I guess you are running hot wallet with v0.12.0.51 or lower and run start-disabled while not completely sync with network.
Please update to v0.12.0.52, UdjinM6 added fixes to make sure that your start-disabled / start-missing can be run only after successfully synced.
In the mean time, try put these lines into your dash.conf
addnode=mn1 ip
addnode=mn2 ip
addnode=mn3 ip
addnode=mn4 ip
addnode=mn5 ip
This will make sure that your MN nodes are quickly get in touch together with your hot wallet , then your hot wallet would know your masternode status faster.
.
Yes v0.12.0.51, thank you. I will correct version and dash.conf
until reindex is finished = sync is done
qwizzie
Well-known member
If you still have problems :
* delete all .dat files (except wallet.dat) in your data directory (not in block chain, just in data directory)
* upgrade to .53 on both cold and hot wallet
* give sync masternode winners at least 15 minutes to fully sync van 75% to 100%
If no problems pls just update to .53 (.52 has high CPU bug), download from official source
(https://www.dashpay.io/downloads/)
* delete all .dat files (except wallet.dat) in your data directory (not in block chain, just in data directory)
* upgrade to .53 on both cold and hot wallet
* give sync masternode winners at least 15 minutes to fully sync van 75% to 100%
If no problems pls just update to .53 (.52 has high CPU bug), download from official source
(https://www.dashpay.io/downloads/)
rango
Active member
Solaso
We released a new masternode monitoring service 2 weeks ago (dashwhale.org). If you have problems keeping you masternodes running, it might be a good idea to use this service to get automatically notified in case of an error. A bunch of parameters are checked to ensure your masternode is healthy.
We released a new masternode monitoring service 2 weeks ago (dashwhale.org). If you have problems keeping you masternodes running, it might be a good idea to use this service to get automatically notified in case of an error. A bunch of parameters are checked to ensure your masternode is healthy.
Why my mn's started again after command start-disabled? That mn's is worked fine and win once. All wallets latest version 55 local and server. Yesterday all work fine
14:18:04
masternode start-disabled
14:18:04
{
"overall" : "Successfully started 2 masternodes, failed to start 0, total 2",
"detail" : {
"status" : {
"alias" : "mn1",
"result" : "successful"
},
"status" : {
"alias" : "mn2",
"result" : "successful"
},
"
14:18:04
masternode start-disabled
14:18:04
{
"overall" : "Successfully started 2 masternodes, failed to start 0, total 2",
"detail" : {
"status" : {
"alias" : "mn1",
"result" : "successful"
},
"status" : {
"alias" : "mn2",
"result" : "successful"
},
"
