v0.10.9.x Help test RC2 forking issues

Status
Not open for further replies.

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
Hm, my node stopped receiving payments around 20 hours ago despite being listed properly in the masternode lists. Does anybody know if I'm doing something wrong or is variance just being a bitch?

5.45.102.169:19999 1 n31jCvcXGCUeFHDSJe6TYMpn7VjX9p3nbd 1402834904354577 136 140615
http://23.23.186.131:1234/address/n31jCvcXGCUeFHDSJe6TYMpn7VjX9p3nbd
My two server has this log. Misbehaving...
I don't know it's related or not .

Cloud you change your masternodeprivkey to new one, and restart masternode ?

http://tdrk.poolhash.org/blocks/masterlist/n31jCvcXGCUeFHDSJe6TYMpn7VjX9p3nbd.txt

Code:
sv01
2014-06-15 11:19:09 accepted connection 5.45.102.169:38552
2014-06-15 11:19:09 send version message: version 70018, blocks=19855, us=54.183.73.24:19999, them=5.45.102.169:38552, peer=5.45.102.169:38552
2014-06-15 11:19:09 receive version message: /Satoshi:0.10.10.1/: version 70018, blocks=19855, us=54.183.73.24:19999, them=5.45.102.169:19999, peer=5.45.102.169:38552
2014-06-15 11:19:10 Sending master node entry - 5.45.102.169:19999
2014-06-15 11:20:37 Misbehaving: 5.45.102.169:38552 (0 -> 20)
2014-06-15 11:21:38 disconnecting node 5.45.102.169:38552

sv02
2014-06-15 11:01:36 AcceptToMemoryPool: 5.45.102.169:19999 /Satoshi:0.10.10.1/ : accepted d0f2e4bd9652beae0fa3831b1b6d8d6d2362b404a8b501f06f4bbbfc1d141ebf (poolsz 2)
2014-06-15 11:18:43 disconnecting node 5.45.102.169:19999
2014-06-15 11:24:15 trying connection 5.45.102.169:19999 lastseen=0.3hrs
2014-06-15 11:24:15 connected 5.45.102.169:19999
2014-06-15 11:24:15 send version message: version 70018, blocks=19857, us=MY_SERVER_IP:19999, them=5.45.102.169:19999, peer=5.45.102.169:19999
2014-06-15 11:24:15 receive version message: /Satoshi:0.10.10.1/: version 70018, blocks=19857, us=MY_SERVER_IP:14830, them=5.45.102.169:19999, peer=5.45.102.169:19999
2014-06-15 11:28:01 Misbehaving: 5.45.102.169:19999 (0 -> 20)
2014-06-15 11:44:15 Misbehaving: 5.45.102.169:19999 (20 -> 40)
2014-06-15 11:50:37 Misbehaving: 5.45.102.169:19999 (40 -> 60)
2014-06-15 11:58:01 Misbehaving: 5.45.102.169:19999 (60 -> 80)
2014-06-15 12:14:16 Misbehaving: 5.45.102.169:19999 (80 -> 100) DISCONNECTING
2014-06-15 12:14:16 disconnecting node 5.45.102.169:19999
 
Last edited by a moderator:

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Well I had one of mine get payed for the first time after 44h, and another got payed within 30mins.

Yes, variance is a b!tch, but I suspect it has to do with testnet low hashrate/high MN count
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Hm, my node stopped receiving payments around 20 hours ago despite being listed properly in the masternode lists. Does anybody know if I'm doing something wrong or is variance just being a bitch?

5.45.102.169:19999 1 n31jCvcXGCUeFHDSJe6TYMpn7VjX9p3nbd 1402834904354577 136 140615
http://23.23.186.131:1234/address/n31jCvcXGCUeFHDSJe6TYMpn7VjX9p3nbd
Well I had one of mine not get payed for 44h, and another got payed within 30mins.
Yes, variance is a b!tch,
 

tralala

New Member
Jun 13, 2014
6
1
3
Just received a payment to the new address, so everything's good again on my side. But it would still have been interesting to understand what was wrong...
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Just received a payment to the new address, so everything's good again on my side. But it would still have been interesting to understand what was wrong...
Nothing is wrong. Its variance. If you got payed, didn't get payed for 20h and then got payed again... its working. Like I said before, I've had a node fire up successful and not get payed for 44hours, and another that got payed within 30 minutes. I'm "sure" on mainnet payouts will be more regular.
That is one of the main reasons p2pool does not get as much adoption as it deserves.
 

tralala

New Member
Jun 13, 2014
6
1
3
Nothing is wrong. Its variance. If you got payed, didn't get payed for 20h and then got payed again... its working. Like I said before, I've had a node fire up successful and not get payed for 44hours, and another that got payed within 30 minutes. I'm "sure" on mainnet payouts will be more regular.
That is one of the main reasons p2pool does not get as much adoption as it deserves.
Yes, I was more talking about the "misbehaving" messages chaeplin found in his logs.
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
oops, my bad. Are you hosting the masternode on a server or at home?
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
TanteStefana I have updated my guide(part 2), Could you check it ?
Do we still need to start the masternode by unlocking the wallet first? I always started mine that way?
darkcoind walletpassphrase "walletpassphrase" 60
darkcoind masternode start mylongpassphrase
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
Well I had one of mine get payed for the first time after 44h, and another got payed within 30mins.

Yes, variance is a b!tch, but I suspect it has to do with testnet low hashrate/high MN count
That shouldn't be a problem though, I mean the hash rate should mirror the difficulty causing a block to be solved every 2.5 minutes, no? Therefore, it shouldn't mater, should it?

BTW, how many masternodes have we got running in testnet?
 
Last edited by a moderator:

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
That shouldn't be a problem though, I mean the hash rate should mirror the difficulty causing a block to be solved every 2.5 minutes, no? Therefore, it shouldn't mater, should it?
Exact, thats what DGW3 is for: Adjust the difficulty to the hashrate --> 2.5min average block time

BTW, how many masternodes have we got running in testnet?
According to http://tdrk.poolhash.org/ we are at 63 currently - 40% of mainnet :)
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
Cool, thanks. Now I'm wondering about NOMP. Is the link on the op for testnet? And do we just use our regular miner and basically hook up like we would for P2pool?

I do see on http://tdrk.poolhash.org/blocks/masterlist.txt that some of the ip addresses have : 0, and are still being timed. But do they stop getting voted on after 1800 seconds? (30 min?) I guess I'm really wondering why after days, they're still not cleared from the list, but now I'm thinking it just wasn't programmed in, this is testnet after all and I'm asking for too much and being a butthead, LOL
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
Cool, thanks. Now I'm wondering about NOMP. Is the link on the op for testnet? And do we just use our regular miner and basically hook up like we would for P2pool?
Yes, as far as i know - give it a try and see if you get shares ;)

I do see on http://tdrk.poolhash.org/blocks/masterlist.txt that some of the ip addresses have : 0, and are still being timed. But do they stop getting voted on after 1800 seconds? (30 min?) I guess I'm really wondering why after days, they're still not cleared from the list, but now I'm thinking it just wasn't programmed in, this is testnet after all and I'm asking for too much and being a butthead, LOL
Well spotted, it's a known bug in RC3 - Evan confirmed that the caching of inactive masternode entries is to agressive in RC3: the entries do not get pruned. As this does not affect the voting (only active nodes get votes) and is more of cosmetic nature, it is categorized as minor bug and will be addressed in RC4.
 
Last edited by a moderator:

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
Do we still need to start the masternode by unlocking the wallet first? I always started mine that way?
darkcoind walletpassphrase "walletpassphrase" 60
darkcoind masternode start mylongpassphrase
I prefer
Code:
darkcoind masternode start `head -1`
Wallet unlocked like 0.0000001 msec of time.

With darkcoind walletpassphrase pass 60, wallet will be unlocked 60 sec long. So do not use.

example
Code:
[email protected]:~> darkcoind walletpassphrase 1 10
[email protected]:~> darkcoind getinfo
{
    "version" : 101000,
    "protocolversion" : 70018,
    "walletversion" : 60000,
    "balance" : 2032.89400000,
    "blocks" : 20315,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.17133109,
    "testnet" : true,
    "keypoololdest" : 1402636400,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "unlocked_until" : 1402904419208,
    "errors" : ""
}
With masternode start pass
Code:
[email protected]:~> darkcoind getinfo && darkcoind masternode start 1 && darkcoind getinfo
{
    "version" : 101000,
    "protocolversion" : 70018,
    "walletversion" : 60000,
    "balance" : 2032.89400000,
    "blocks" : 20315,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.17133109,
    "testnet" : true,
    "keypoololdest" : 1402636400,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "unlocked_until" : 0,
    "errors" : ""
}
successfully started masternode
{
    "version" : 101000,
    "protocolversion" : 70018,
    "walletversion" : 60000,
    "balance" : 2032.89400000,
    "blocks" : 20315,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.17133109,
    "testnet" : true,
    "keypoololdest" : 1402636400,
    "keypoolsize" : 101,
    "paytxfee" : 0.000000001
    "mininput" : 0.00001000,
    "unlocked_until" : 0,
    "errors" : ""
}
Is it unlocked ?
 

daaarkcoins

Member
May 21, 2014
95
40
68
Do we still need to start the masternode by unlocking the wallet first? I always started mine that way?
darkcoind walletpassphrase "walletpassphrase" 60
darkcoind masternode start mylongpassphrase
You don't need to unlock it first. Also you should either use darkcoind masternode start $(head -1) or clear your bash history afterwards with history -c

edit: chaeplin said it already :S
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Reporting 24h activity.

This address is the one where I activated a 2k ticket to masternode, then dropped 1k (My previously described Masternode_A)... I remember it took quite some hours to get first payout
http://23.23.186.131:1234/address/mpv3jJQi9otaVTDhheHyKP7k8toLd73ott

This is the address is the regular 1k masternode, that got payed within 30 minutes of being active (My Masternode_B)
http://23.23.186.131:1234/address/mtSQDmxDEY69Kn31uo6aRJHxD1nYdFFzvo

What do you guys think? Coincidence? B is getting more than double than A.
 
Last edited by a moderator:

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
I have installed new nomp.
No need to patch to support 20% Masternode payment.
(20% payment support is already merged WOW)

http://tdrk.poolhash.org/
nomp2 is the one.

I will change reward percent to 10.

What's gonna be ?

Probably banned ?


Result :
log in nomp
Code:
2014-06-16 20:42:38 [Pool][darkcoin] (Thread 2) Daemon instance 0 rejected a supposedly valid block
log in darkcoind
Code:
2014-06-16 11:42:38  BAD MASTERNODE PAYMENT DETECTED:  1510100000
;D

changed to */5 ;D
 
Last edited by a moderator:
  • Like
Reactions: vertoe and flare

elbereth

Active Member
Dash Support Group
Mar 25, 2014
461
484
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
Worries me a bit that the official explorer is down, no official news about 0.9.10.1 and 0.10.10.1 versions and no signs of Evan... I hope it is not some bad news coming.
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
Worries me a bit that the official explorer is down, no official news about 0.9.10.1 and 0.10.10.1 versions and no signs of Evan... I hope it is not some bad news coming.
Nothing to worry about yet, Evan is alive and kicking.

Code:
commit 5409bba62b9003d16a1ffa8d0d4674cba69e455d
Author: Evan Duffield <[email protected]>
Date:   Sat Jun 14 20:22:03 2014 -0700

    Cleaned up voting debug
The official explorer being down is sad, unfortunately i don't have access to the server to fix it.
 
  • Like
Reactions: chaeplin

TsuyokuNaritai

Active Member
May 24, 2014
181
102
103
Worries me a bit that the official explorer is down, no official news about 0.9.10.1 and 0.10.10.1 versions and no signs of Evan... I hope it is not some bad news coming.
Jeez, let the guy have a day off! Even superheroes need to sleep occasionally. :tongue:
 

elbereth

Active Member
Dash Support Group
Mar 25, 2014
461
484
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
No problem in taking a day off (or even the weekend off). It is just that normally with Evan, no news = something is in development. :D
Not blaming anyone or anything, just stating my worries 4 days prior to the hard fork (and I remember the last hard forks, they were not smooth to say the least).
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
I prefer
Code:
darkcoind masternode start `head -1`
Wallet unlocked like 0.0000001 msec of time.

With darkcoind walletpassphrase pass 60, wallet will be unlocked 60 sec long. So do not use.

example
Code:
[email protected]:~> darkcoind walletpassphrase 1 10
[email protected]:~> darkcoind getinfo
{
    "version" : 101000,
    "protocolversion" : 70018,
    "walletversion" : 60000,
    "balance" : 2032.89400000,
    "blocks" : 20315,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.17133109,
    "testnet" : true,
    "keypoololdest" : 1402636400,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "unlocked_until" : 1402904419208,
    "errors" : ""
}
With masternode start pass
Code:
[email protected]:~> darkcoind getinfo && darkcoind masternode start 1 && darkcoind getinfo
{
    "version" : 101000,
    "protocolversion" : 70018,
    "walletversion" : 60000,
    "balance" : 2032.89400000,
    "blocks" : 20315,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.17133109,
    "testnet" : true,
    "keypoololdest" : 1402636400,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "unlocked_until" : 0,
    "errors" : ""
}
successfully started masternode
{
    "version" : 101000,
    "protocolversion" : 70018,
    "walletversion" : 60000,
    "balance" : 2032.89400000,
    "blocks" : 20315,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.17133109,
    "testnet" : true,
    "keypoololdest" : 1402636400,
    "keypoolsize" : 101,
    "paytxfee" : 0.000000001
    "mininput" : 0.00001000,
    "unlocked_until" : 0,
    "errors" : ""
}
Is it unlocked ?
Ah, now I understand what that is doing! Thank you very much!
 
  • Like
Reactions: chaeplin

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
Worries me a bit that the official explorer is down, no official news about 0.9.10.1 and 0.10.10.1 versions and no signs of Evan... I hope it is not some bad news coming.
Thank goodness he take some time off! Usually Sunday, hopefully Saturdays too! This was a Holiday weekend with Father's day yesterday, so hopefully Evan has a father to spend time with :D
 
  • Like
Reactions: chaeplin and flare
Status
Not open for further replies.