Checked this against ALL my customers nodes, i don't get a single entry in any debug.log ...
v0.10.16 - Onyx v2
- Thread starter eduffield
- Start date
wonder what's up with these..says inactive for active duration, but status active.
Masternode IP
ortPort Check (Next check)VersionMasternode PubkeyBalanceActive DurationLast SeenCountryStatus
(Active Score)
104.131.134.41:9999Open (42m52s)0.10.16.11XtfLy5bx2WUN43Uto2Hq2WozAVhF5ShtWE[1][2]1,000.000Inactive6m48s
United StatesActive (100%)
104.131.236.114:9999Open (42m16s)0.10.16.11XdAdrkjBbSMSe8ofVtS7S4PPQXzFbBwsSi[1][2]1,000.000Inactive6m47s
United StatesActive (100%)
107.170.13.222:9999Open (42m17s)0.10.16.11XsmWeGdR6ZQLZUJRi7ut16keKMARssNZVy[1][2]1,000.000Inactive6m46s
United StatesActive (100%)
107.170.157.166:9999Open (42m17s)0.10.16.11XtcEBhogcKvheZ41hAL3HLVeEAcWpED13z[1][2]1,000.000Inactive6m45s
United StatesActive (100%)
107.170.196.35:9999Open (42m17s)0.10.16.11XkQnk5U9fUWhvrnn4uKPGZn3wj3UKxvuhX[1][2]1,000.000Inactive6m48s
United StatesActive (100%)
Masternode IP
ortPort Check (Next check)VersionMasternode PubkeyBalanceActive DurationLast SeenCountryStatus(Active Score)
104.131.134.41:9999Open (42m52s)0.10.16.11XtfLy5bx2WUN43Uto2Hq2WozAVhF5ShtWE[1][2]1,000.000Inactive6m48s
104.131.236.114:9999Open (42m16s)0.10.16.11XdAdrkjBbSMSe8ofVtS7S4PPQXzFbBwsSi[1][2]1,000.000Inactive6m47s
107.170.13.222:9999Open (42m17s)0.10.16.11XsmWeGdR6ZQLZUJRi7ut16keKMARssNZVy[1][2]1,000.000Inactive6m46s
107.170.157.166:9999Open (42m17s)0.10.16.11XtcEBhogcKvheZ41hAL3HLVeEAcWpED13z[1][2]1,000.000Inactive6m45s
107.170.196.35:9999Open (42m17s)0.10.16.11XkQnk5U9fUWhvrnn4uKPGZn3wj3UKxvuhX[1][2]1,000.000Inactive6m48s
I also have a script checking activity of MN's and winners. After I stopped running the script, the problem goes away. Do you want to try stop running your script? There may be some bug that kicks the MN off the list after certain query limit.
EDIT: Have been running without being kicked off the network for six hours now. The script worked perfectly with 0.10.15.21. So, I'm sure it is not the script that is buggy. I also wait 10 seconds after stop and 60+ seconds after start.
Last edited by a moderator:
It's ok because you have correct CActiveMasternode::RegisterAsMasterNode() messages
The only way I see for your nodes to getaway with this is https://github.com/darkcoin/darkcoin/blob/master/src/activemasternode.cpp#L270
But how do they stay online then?...
We need eduffield here...
Only one way for them to stay online in this situation - they are "in the future".
We need a check like this https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L178-L181 to be implemented in CMasterNode::Check() https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L464 and maybe somewhere in dsee message processing.
EDIT: fixed -->Check
EDIT2: http://jira.darkcoin.qa/browse/DRK-124
We need a check like this https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L178-L181 to be implemented in CMasterNode::Check() https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L464 and maybe somewhere in dsee message processing.
EDIT: fixed -->Check
EDIT2: http://jira.darkcoin.qa/browse/DRK-124
Last edited by a moderator:
I've checked the time, both masternodes and local laptop - all in sync, despite being different timezones.
That's confusing me cause I have no more ideas..
The last one. From somewhere else (not from the node you check):
Code:
darkcoind masternode list lastseen | grep "IP_OF_SOME_NODE"http://www.onlineconversion.com/unix_time.htm
Cool, is this rumor or fact?I guess Evan will start to squash some old bugs once he is satisfied how new Darksend implementation works
EDIT: I didn't remove peers.dat.... will do this now
Me neither.
But what's REALLY odd:
I don't get ONE single CActiveMasternode::RegisterAsMasterNode() entry in the logs of 3 of my Masternodes.
Nothing. Not a single one.
And there should plenty of them, because these Masternodes are listed as active.
I'm using the official Linux 64 bit binaries.
I think I'll build them myself from GIT like you did, maybe there's a difference...
Are there other instructions to follow when updating to 16.11?My qt wallet stuck today at "1 hour behind". Closed, opened it again and it synced.
I guess Evan will start to squash some old bugs once he is satisfied how new Darksend implementation works
EDIT: I didn't remove peers.dat.... will do this now
Do I remove peers.dat on both local and server?
There is no really need for that I believe, it should just help to avoid "old" clients so wallet will not try to connect to them, fail
and remove them from the list one by one.But in a matter of testing and looking in debug.log to find something unusal this might help. But I see nothing unusual so far....
You can do that, no harm, just in case, i always delete peers.dat from both local and remote when updating.
Even with the self-build binaries there's no difference.
I think I'll add some lines of additional Log, build again and see what's going on...
Oh, so this is where ya'all are talking
Has Evan uploaded 10.16.12 yet? He said he fixed mixing issues on BTC this morning...
Has Evan uploaded 10.16.12 yet? He said he fixed mixing issues on BTC this morning...
Okay, adding a ton of my own debug info tracked this one down, and even when I'm a bit ashamed to admit it's user error the implications of my findings are too interesting to not share them here:
- I have a hot/cold setup for my Masternodes.
- I have a script which updates my remote Masternodes automatically. The binary, a generated darkcoin.conf and a couple of other things. Somehow about one month ago the configuration entry "masternode=1 got lost, so from that day on all of my hot Masternodes did NOT have that line in darkcoin.conf. :facepalm: (the cold ones have, though)
- This means CActiveMasternode::RegisterAsMasterNode() is never successdully executed:
- Private key is not checked
- External IP and port is not checked
- Wallet lock is not checked
- vin is not checked
- Masternode is not relayed to the peers
- A ton of other things...
- Most of the above is not really THAT important for a hot Masternode to run properly , but I still fail to see why my Masternodes were seen (and paid of course) by the rest of the network at all.
10.16.12 Onyx V2 - Masternode Operators Please Update
- Fixed mixing issues on the network
Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.12-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.12-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.12-linux.tar.gz
- Fixed mixing issues on the network
Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.12-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.12-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.12-linux.tar.gz
denom working well done evan.
*Edit* have been hit with two 0.1 fees
*edit2* 3 fees and only 1 round complete
Will turn off and wait a few days
*Edit 3* I see success reported on bct and others are successful.
So guess I've just been really unlucky. 3 fees/2rounds
well done evan.*Edit* have been hit with two 0.1 fees
*edit2* 3 fees and only 1 round complete
Will turn off and wait a few days
*Edit 3* I see success reported on bct and others are successful.
So guess I've just been really unlucky. 3 fees/2rounds
Last edited by a moderator:
There are some checks of vin in ProcessMessageMasternode (on receiver side) and in ThreadCheckDarkSendPool actually so it should be ok.Okay, adding a ton of my own debug info tracked this one down, and even when I'm a bit ashamed to admit it's user error the implications of my findings are too interesting to not share them here:
- I have a hot/cold setup for my Masternodes.
- I have a script which updates my remote Masternodes automatically. The binary, a generated darkcoin.conf and a couple of other things. Somehow
- This means CActiveMasternode::RegisterAsMasterNode() is never successdully executed:
- Private key is not checked
- External IP and port is not checked
- Wallet lock is not checked
- vin is not checked
- Masternode is not relayed to the peers
- A ton of other things...
- Most of the above is not really THAT important for a hot Masternode to run properly , but I still fail to see why my Masternodes were seen (and paid of course) by the rest of the network at all.
When there is no masternode=1 on remote node it will check keys and vin https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L129
update lastTimeSeen and add itself into MN list https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L141-L142
and only then it will fail https://github.com/darkcoin/darkcoin/blob/master/src/activemasternode.cpp#L296
but still relay itself to others https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L149
So you'll get your 70 minutes and then your node will become inactive.
Definitely should fail faster
EDIT: http://jira.darkcoin.qa/browse/DRK-125
Last edited by a moderator: