v0.10.16 - Onyx v2

flare said:
Checked back with Evan: The issues with MN startup will level out as network updates. Currently the startup messages (dsee) do not propagated properly through the network. This is due to lots of nodes updating / being outdated :)
Click to expand...
So if you update the remote and local and issue masternode start from local, even if you don't get anything, you should be fine eventually or what?
 
flare said:
Checked back with Evan: The issues with MN startup will level out as network updates. Currently the startup messages (dsee) do not propagated properly through the network. This is due to lots of nodes updating / being outdated :)
Click to expand...
Hope so. Looks nasty out there. Masternode list has gone crazy lately. One MN has this:
Code: 
ubuntu@108:~/.darkcoin$ ./darkcoind masternode list
{
  "54.172.7.66:9999" : 0,
  "54.77.176.186:9999" : 0,
  "54.191.252.10:9999" : 0,
  "178.62.128.51:9999" : 0,
  "54.171.125.155:9999" : 0,
  "178.62.183.183:9999" : 0,
  "108.61.198.250:9999" : 0,
  "95.85.54.64:9999" : 0,
  "108.61.224.181:9999" : 0,
  "54.69.96.201:9999" : 0,
  "108.61.221.47:9999" : 0,
  "178.62.171.227:9999" : 0,
  "178.62.171.69:9999" : 0
}

Another MN has this:
Code: 
ubuntu@108:~/.darkcoin$ ./darkcoind masternode list
{
  "54.172.7.66:9999" : 0,
  "54.171.125.155:9999" : 0,
  "178.62.183.183:9999" : 0,
  "108.61.198.250:9999" : 0,
  "95.85.54.64:9999" : 0,
  "108.61.224.181:9999" : 0,
  "54.69.96.201:9999" : 0,
  "108.61.221.47:9999" : 0,
  "178.62.171.227:9999" : 0,
  "178.62.171.69:9999" : 0,
  "54.171.28.121:9999" : 1,
  "108.61.198.195:9999" : 1,
  "108.61.211.16:9999" : 1
}
 
I think there still may be issues with the masternode list. I just checked one of my nodes that was showing like 30 nodes, and it is now showing only 6.
 
My masternodes that were showing in the list and grepping 1 are now kicking offline. Like darkcoind is timing out and the process needs to be manually restarted.
 
Like i say every time when protocol version changes: update your node and leave it for 24hrs - the network needs to rebuild, at least 1200 x 8 connections have to be reestablished ^^
 
oblox said:
So if you update the remote and local and issue masternode start from local, even if you don't get anything, you should be fine eventually or what?
Click to expand...
Not fully, but basically: wait 24hrs and then start your node again (if needed)
 
just checked with 15.21 and my MN appear there as online ("1") while checkin with 16.5 it's not even in the list
 
flare said:
Not fully, but basically: wait 24hrs and then start your node again (if needed)
Click to expand...
So I'm better off stopping all the remote daemons and waiting or should I keep the remotes running and initiate the masternode start in 24 hours.
 
oblox said:
So I'm better off stopping all the remote daemons and waiting or should I keep the remotes running and initiate the masternode start in 24 hours.
Click to expand...
It is better if you keep the daemons running so the network grows. Try to start from local wallets also. Worst case scenario they shut down. Best case you get it working and don't have to start again tomorrow.

Sidenote: I saw a few hours ago the testing thread and scheduled some time tonight to go over it and set up a masternode in testnet and start playing. Now I log in and testing is already done and I need to update masternodes... this is amazing!! thanks to those who took part!!
 
Updated both local and remote.
Local QT reports my MN started successfully and has status "1"
Remote does not show itself on "masternode list"

EDIT
---------
Masternode List shows 1 "1" and 1 "0". Neither of them mine.
 
Last edited by a moderator:
DrkMiner said:
Yes, same issue. I'm updating few nodes. After restart they don't show on the list.

grep HotCold .darkcoin/debug.log Doesn't return result.
Click to expand...

spatula said:
I seem to be having issues with my masternodes showing up in the list. When i start from the wallet it says its successful.
Click to expand...

To clarify:

Starting up a hot/cold masternode requires that the network can propagate messages for the new protocol. That takes some time. However, if you're running a non hot/cold setup, your daemon will continue to attempt to propagate one until it can.

It just takes some time for the network to update. I'll add some code for the next release that will allow backwards compatibility of the masternode messages, that would be a huge improvement.
 
I just updated my MN. Seems to have come up properly but I'm only seeing three MNs on the masternode list on my VPS (including mine). The Darkcoin Masternode Ninja page seems to have lost almost all of the masternodes too. Based on previous comments, I'm aware the new version needs to propagate connections but is this right?

20141114 Only two masternodes showing during 0.10.16.5 network update.jpg
 
BCT site is down..also my amazon AWS keeps becoming unavailable. Maybe its a wider outage somewhere in the interwebz.
 
You must log in or register to reply here.
Back
Top