Problems after upgrading to 12.2

I also added my other masternode as a connection with addnode. The reply was silent.
Then I run again the getinfo and the getchaintips. Getchaintips did not change. Getinfo lowered the number of connection from 23 to 21
{
"version": 120201,
"protocolversion": 70208,
"walletversion": 61000,
"balance": 0.00000000,
"privatesend_balance": 0.00000000,
"blocks": 769068,
"timeoffset": 0,
"connections": 21,
"proxy": "",
"difficulty": 35181684.73744042,
"testnet": false,
"keypoololdest": 1508498810,
"keypoolsize": 1001,
"paytxfee": 0.00000000,
"relayfee": 0.00010000,
"errors": ""
}

Thanks for the help. It appears to be still blocked.

Should I just keep adding masternodes?
 
As far as I understand it, he told you to add some random ips of masternodes as your peers, so that you increase the chance to discover a good masternode.
Adding your other masternode which was also a bad one, was meaningless.
 
demo said:
As far as I understand it, he told you to add some random ips of masternodes as your peers, so that you increase the chance to discover a good masternode.
Adding your other masternode which was also a bad one, was meaningless.
Click to expand...

no, no, my other one is working now. Sorry, I forgot to mention it.
 
Pietro Speroni said:
So, getinfo now gives:

{
"version": 120201,
"protocolversion": 70208,
"walletversion": 61000,
"balance": 0.00000000,
"privatesend_balance": 0.00000000,
"blocks": 769068,
"timeoffset": 0,
"connections": 23,
"proxy": "",
"difficulty": 35181684.73744042,
"testnet": false,
"keypoololdest": 1508498810,
"keypoolsize": 1001,
"paytxfee": 0.00000000,
"relayfee": 0.00010000,
"errors": ""
}

While getchaintips gives:
{
"height": 769079,
"hash": "000000000000008754811f3bbaacd16d0b3afef07b6a498626bab80fa7027155",
"difficulty": 15215184.12686991,
"chainwork": "0000000000000000000000000000000000000000000000598465deb4ec8673b1",
"branchlen": 11,
"status": "headers-only"
},

{
"height": 769068,
"hash": "00000000000000233e44da14628ac182b13df1774b709cb07ea2233444d92e40",
"difficulty": 35181684.73744042,
"chainwork": "000000000000000000000000000000000000000000000059756f5105d3d81a23",
"branchlen": 0,
"status": "active"
},

{
"height": 769066,
"hash": "00000000000000219eb0ff02c8ac196eeaceee1ce7453d228a1af77e129b607f",
"difficulty": 38353722.43502148,
"chainwork": "00000000000000000000000000000000000000000000005971283f0510761f8a",
"branchlen": 1,
"status": "invalid"
}

did I went off into a sidebranch?
Click to expand...
try
./dash-cli mnsync reset
./dash-cli reconsiderblock 00000000000000219eb0ff02c8ac196eeaceee1ce7453d228a1af77e129b607f
./dash-cli clearbanned
 
UdjinM6 said:
try
./dash-cli mnsync reset
./dash-cli reconsiderblock 00000000000000219eb0ff02c8ac196eeaceee1ce7453d228a1af77e129b607f
./dash-cli clearbanned
Click to expand...
Thanks. Now it works. Do you think you could explain me what happened, and how to get out of it another time?
 
Pietro Speroni said:
Thanks. Now it works. Do you think you could explain me what happened, and how to get out of it another time?
Click to expand...
Code: 
dash-cli masternode winners 5000 | grep 769066
12.1:
Code: 
"769066": "XwkuyuADEqbwvJudgNVXTDvhDLSyKQhwns:4, XhJEHGdx7Dd7yZtpuaRY9R5VNDfgn9kfqS:6",
12.2:
Code: 
"769066": "XwkuyuADEqbwvJudgNVXTDvhDLSyKQhwns:4, XhJEHGdx7Dd7yZtpuaRY9R5VNDfgn9kfqS:3",
actual block, https://explorer.dash.org/block/00000000000000219eb0ff02c8ac196eeaceee1ce7453d228a1af77e129b607f:
Code: 
XvhExSNNr97U1ZenWFjJmgD8wc7v88ZUF7: 1.80849243
XwkuyuADEqbwvJudgNVXTDvhDLSyKQhwns: 1.8084924
i.e. miner paid to the other MN and 12.1 nodes rejected it and forked off.
That's a "normal" situation for migration period when spork8 is ON. We tried to recover from it quickly turning spork8 OFF and issuing spork12 to replay few recent blocks but some nodes isolated themselves too quickly it seems. https://www.dash.org/forum/threads/version-12-2-release.17807/page-3#post-146139
 
UdjinM6 said:
Code: 
dash-cli masternode winners 5000 | grep 769066
12.1:
Code: 
"769066": "XwkuyuADEqbwvJudgNVXTDvhDLSyKQhwns:4, XhJEHGdx7Dd7yZtpuaRY9R5VNDfgn9kfqS:6",
12.2:
Code: 
"769066": "XwkuyuADEqbwvJudgNVXTDvhDLSyKQhwns:4, XhJEHGdx7Dd7yZtpuaRY9R5VNDfgn9kfqS:3",
actual block, https://explorer.dash.org/block/00000000000000219eb0ff02c8ac196eeaceee1ce7453d228a1af77e129b607f:
Code: 
XvhExSNNr97U1ZenWFjJmgD8wc7v88ZUF7: 1.80849243
XwkuyuADEqbwvJudgNVXTDvhDLSyKQhwns: 1.8084924
i.e. miner paid to the other MN and 12.1 nodes rejected it and forked off.
That's a "normal" situation for migration period when spork8 is ON. We tried to recover from it quickly turning spork8 OFF and issuing spork12 to replay few recent blocks but some nodes isolated themselves too quickly it seems. https://www.dash.org/forum/threads/version-12-2-release.17807/page-3#post-146139
Click to expand...
Thank you very much @UdjinM6 .

Actually few hours later the masternode broke again. So I started again wondering if I were going to find a way to solve everything by myself this time. But this time I worked fine. Also the other node this morning needed a restart on my computer while the server was running fine. It's all very mysterious still. :).

Maybe @strophy is right and I should upgrade to servers more powerful. But when I look at the statistics it still looks it is only using a fraction of the power and memory available.
 
Upgrading your server to the recommended spec will likely cost you $5 extra per month. Not upgrading and continuously being sent to the back of the queue due to memory spikes will currently cost you well over $3000 per month. It's an easy choice ;)
 
strophy said:
Upgrading your server to the recommended spec will likely cost you $5 extra per month. Not upgrading and continuously being sent to the back of the queue due to memory spikes will currently cost you well over $3000 per month. It's an easy choice ;)
Click to expand...
5$ more :eek:???? WTF I knew this masternode business had hidden costs!
Btw, do you know if it is possible to upgrade on vultr without setting everything up from the beginning?
 
Haha, yes it is possible to upgrade on Vultr, just shut down your server first, then log in and go to Settings > Change Plan. It is not possible to downgrade again after an upgrade, but that's not really an issue.
 
Sometimes node crashes due to lack of RAM/swap (OOM kills it to save the system). I'd recommend to have at least 1GB RAM and 4GB swap, this should be enough even for a relatively long time burst of 2MB blocks and lots of proposals/votes etc.
 
You must log in or register to reply here.
Back
Top