v0.10.9.x Help test RC2 forking issues

flare · Jun 7, 2014

eduffield said:
*** PLEASE UPDATE TO 9.5.5 OR 10.9.5 **

This update fixes the rest of the ghost masternode issue. The code wasn't properly marking masternodes that had moved funds. We'll let this run for a day then I'll merge this into masternode and we'll all start updating.

Upated my nodes to 10.9.6 and killed one daemon (184.73.179.196) at 07:20:45 UTC

At 08:44:12 UTC (85min later) the node still shows up in the masternode list as active.

Network seems to have acquired version 0.x.9.5+ to about >50% right now

Code:

      1         "subver" : "/Satoshi:0.9.5.3/",
      2         "subver" : "/Satoshi:0.9.5.5/",
      1         "subver" : "/Satoshi:0.10.9.2/",
      1         "subver" : "/Satoshi:0.10.9.3/",
      3         "subver" : "/Satoshi:0.10.9.4/",
     11         "subver" : "/Satoshi:0.10.9.5/",
      3         "subver" : "/Satoshi:0.10.9.6/",

Let's see if this resolves through time, or if more tweaking to the masternode code is needed.

flare · Jun 7, 2014

chaeplin said:
(10.9.6 !!!)

Yes, seems Evan recently updated the download binary to 0.10.9.6/0.9.9.6 - 12 hours ago i downloaded v0.10.9.5

Even github/forkfix is only at 0.9.9.5 up till now

eduffield · Jun 7, 2014

***** Update to 9.5.6 or 10.9.6 ********
This update provides hot/cold masternode support!

To setup, copy the configuration options masternode=1 and masternodeprivkey=KEY from your daemon with the 1000DRK to the hot daemon.
Add masternodeaddr=HOTMASTERNODEIP:19999 to your COLD daemon.
On the hot daemon run "masternode debug" you should see "Missing masternode input, please look at the documentation for instructions on masternode creation"
On the cold daemon run "masternode start"
In the debug log of the hot daemon you should see "CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon."
You may now turn off the cold node, but DO NOT move the funds. This will immediately disable your masternode.

------------------------

There's also a fix for ghost masternodes (there was still a problem), TTL is now 30 minutes and the protocol is not backwards compatible. So please update!

Binaries (stable)
http://www.darkcoin.io/downloads/forkfix/darkcoin-qt
http://www.darkcoin.io/downloads/forkfix/darkcoind

RC3 Binaries ( masternodes )
http://www.darkcoin.io/downloads/rc3/darkcoin-qt
http://www.darkcoin.io/downloads/rc3/darkcoind

FoldingTime · Jun 7, 2014

Awesome !!!!!!!!!!!!!!

I've just done the upgrade for my Masternode and got the results you mentioned so all looks good. However, I'm getting lots of the following in my debug.log. Anything to be concerned about?

Code:

2014-06-07 16:06:55 disconnecting node 92.222.7.210:19999
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED

eduffield · Jun 7, 2014

FoldingTime said:

Awesome !!!!!!!!!!!!!!

I've just done the upgrade for my Masternode and got the results you mentioned so all looks good. However, I'm getting lots of the following in my debug.log. Anything to be concerned about?

Code:

2014-06-07 16:06:55 disconnecting node 92.222.7.210:19999
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:55 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED
2014-06-07 16:06:56 ProcessMessage(dssu, 13 bytes) FAILED

That's fine, it's the incompatible protocol.

flare · Jun 7, 2014

eduffield said:
***** Update to 9.5.6 or 10.9.6 ********

I updated my nodes to 10.9.6, and my debug.log gets spammed now - hundreds of the same message

Code:

daemon.CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold
[...]

Seems there is a flaw in the code when running in NON hot/cold setup :smile:

yidakee · Jun 7, 2014

eduffield said:
That's fine, it's the incompatible protocol.

Going to update ASAP. God bless 3G networks right now...

eduffield · Jun 7, 2014

flare said:

I updated my nodes to 10.9.6, and my debug.log gets spammed now - hundreds of the same message

Code:

daemon.CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.
CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold
[...]

Seems there is a flaw in the code when running in NON hot/cold setup :smile:

Hmm, I'll check that out

eduffield · Jun 7, 2014

yidakee said:
Going to update ASAP. God bless 3G networks right now...

You need to generate one key, and your hot/cold daemons should share that key.

flare · Jun 7, 2014

eduffield said:
Hmm, I'll check that out

Thanks - debug.log growing 1M per minute in size currently with these messages. Strange enough: Only one node is showing this behaviour...

EDIT: This is what i get during startup of the node. I dont understand why your node is misbehaving?!

Code:

[...]
2014-06-07 17:49:13 send version message: version 70016, blocks=15636, us=184.73.179.148:19999, them=23.23.186.131:19999, peer=23.23.186.131:19999
2014-06-07 17:49:13 Misbehaving: 23.23.186.131:19999 (0 -> 1)
2014-06-07 17:49:13 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-07 17:49:13 Misbehaving: 23.23.186.131:19999 (1 -> 2)
2014-06-07 17:49:13 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-07 17:49:13 Misbehaving: 23.23.186.131:19999 (2 -> 3)
2014-06-07 17:49:13 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-07 17:49:13 Misbehaving: 23.23.186.131:19999 (3 -> 4)
2014-06-07 17:49:13 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-07 17:49:13 Added time data, samples 2, offset +0 (+0 minutes)
2014-06-07 17:49:13 receive version message: /Satoshi:0.10.9.6/: version 70016, blocks=15637, us=184.73.179.148:38655, them=23.23.186.131:19999, peer=23.23.186.131:19999
2014-06-07 17:49:13 ProcessSyncCheckpoint: sync-checkpoint at 0000000043ced0aaedb5aa8db15acfb9c0d70bf2db02436f34ccc936adf7716e
2014-06-07 17:49:13 dsee - Got NEW masternode entry 184.73.179.148:19999
2014-06-07 17:49:13 dsee - Accepted masternode entry -1 -1
2014-06-07 17:49:13 CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.dsee - Got NEW masternode entry 184.73.179.187:19999
2014-06-07 17:49:14 dsee - Accepted masternode entry 3 0

EDIT2:

Masternode list got very exclusive :grin:
--> http://tdrk.poolhash.org/blocks/masterlist.txt

Code:

    37.187.47.129:19999 : 0,
    184.73.179.148:19999 : 0,
    184.73.179.187:19999 : 1,
    184.73.179.196:19999 : 0

FoldingTime · Jun 7, 2014

flare said:
Masternode list got very exclusive :grin:
--> http://tdrk.poolhash.org/blocks/masterlist.txt

Code:

37.187.47.129:19999 : 0, 184.73.179.148:19999 : 0, 184.73.179.187:19999 : 1, 184.73.179.196:19999 : 0

Yes, as a result I'm getting truck loads of payments :grin:

My IP has a :0 at the end in your list, however, I'm getting the payments through so looks like an OK status.

yidakee · Jun 7, 2014

Yey!!

local masternode list, mine shows up!

{
"184.73.179.148:19999" : 1,
"184.73.179.187:19999" : 1,
"54.255.159.230:19999" : 1

Not yet on http://tdrk.poolhash.org/blocks/masterlist.txt .. will try to time it, my turn cooking dinner

TanteStefana · Jun 7, 2014

I updated to 10.9.6 yesterday, is that the same daemon or was something changed but not the number?

flare · Jun 7, 2014

FoldingTime said:
Yes, as a result I'm getting truck loads of payments :grin:

Same for me, my nodes got paid 8 out of last 15 blocks :grin:

flare · Jun 7, 2014

TanteStefana said:
I updated to 10.9.6 yesterday, is that the same daemon or was something changed but not the number?

This one is new, internal version numer is v0.10.9.6-2-ge1acf1a-beta, yesterday was v0.10.9.6-beta

Code:

:~/.darkcoin$ strings darkcoind | grep v0.1
v0.10.9.6-2-ge1acf1a-beta

Code:

~/.darkcoin$ strings darkcoind.old | grep v0.1
v0.10.9.6-beta

yidakee · Jun 7, 2014

flare said:
Same for me, my nodes got paid 8 out of last 15 blocks :grin:

damn, so soon? I still haven't. Here is my current list on the hot daemon.

ubuntu@ip-172-31-3-203:~/.darkcoin/testnet3$ darkcoind masternode list
{
"184.73.179.148:19999" : 1,
"184.73.179.187:19999" : 0,
"54.255.159.230:19999" : 1,
"184.73.179.196:19999" : 0,
"37.187.47.129:19999" : 0

I could have sworn they were all :1 not 5 mins ago... Mine is xx.xx.xx.230

chaeplin · Jun 7, 2014

http://drk.poolhash.org/masternode.html updated.
last 24hr supply : 2789
no of masternode : 286

(last 24hr supply * 0.2) / no of masternode = 1.9xx ( payment per node / 1 day)

eduffield · Jun 7, 2014

Fixing the bug with the massive amount of spam, should be compiled in a sec

flare · Jun 7, 2014

chaeplin said:
http://drk.poolhash.org/masternode.html updated.
last 24hr supply : 2789
no of masternode : 286

(last 24hr supply * 0.2) / no of masternode = 1.9xx ( payment per node / 1 day)

To good to be true :grin:

And i hardly doubt that there are really 286 nodes active at the moment, as my three nodes (._.179.x) are offline on mainnet since 5 days but still in the list. So i expect a even better ROI when the new client is rolled out to mainnet - after fixing the last bugs :smile:

yidakee · Jun 7, 2014

No payments for 31 minutes, time it took to get on http://tdrk.poolhash.org/blocks/masterlist.txt

54.255.159.230:19999 : 1,
184.73.179.148:19999 : 0,
184.73.179.196:19999 : 0

v0.10.9.x Help test RC2 forking issues

Well-known member

Well-known member

Core Developer

Member

Core Developer

Well-known member

Well-known member

Core Developer

Core Developer

Well-known member

Member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Core Developer

Well-known member

Well-known member