v0.10.9.x Help test RC2 forking issues

jimbit · Jun 13, 2014

atavacron said:
I'm home for a about an hour.
I'm going to bring up all of my testnet masternodes. Hopefully nothing out of the ordinary will happen. Lets find out.

I guess I will fire mine back up

edit:
Looks like I received a payment, even tho I have been off for 24 hours.

I restarted my testnet MN. I had to change the IP (restart instance)

getinfo:
{
"version" : 101000,
"protocolversion" : 70018,
"walletversion" : 60000,
"balance" : 8026.72629998,
"blocks" : 18962,
"timeoffset" : 0,
"connections" : 10,
"proxy" : "",
"difficulty" : 0.20762775,
"testnet" : true,
"keypoololdest" : 1401626368,
"keypoolsize" : 99,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}
ubuntu@ip-10-252-154-79:~/.darkcoin$ darkcoind masternode list
{
"54.203.87.19:19999" : 1
}

This node has been shut down for about 24 hours.. when I started it and did a list transactions, I see I received a payment just 12 blocks ago.

{
"account" : "",
"address" : "mw23256bSTqEkP6ThTRrY3KNicB9cfwzLR",
"category" : "immature",
"amount" : 30.20000000,
"confirmations" : 12,
"generated" : true,
"blockhash" : "000000022b7ed5ee99a7b4f47677eebec03aa1126ccb9f63158a3105dd486ae8",
"blockindex" : 0,
"blocktime" : 1402688846,
"txid" : "5b04644a812ac0bdfb0649c76c40c920351f2e38b5ae6fbee5692de283b2ced0",
"time" : 1402688846,
"timereceived" : 1402691092
}

yidakee · Jun 13, 2014

Both my local/remote are on DarkCoin version v0.10.9.13-beta
Fired up my local node up, from a perfectly shutdown VM Ubuntu 10.04.

ocaldarknode@ubuntu:~$ darkcoind
DarkCoin server starting
localdarknode@ubuntu:~$ darkcoind masternode debug
successfully started masternode
localdarknode@ubuntu:~$ darkcoind listtransactions
[
{
"account" : "0",
"address" : "mrPbaoAeVVeaiuezEmqs7zQimHHcAtKAqq",
"category" : "receive",
"amount" : 1000.00000000,
"confirmations" : 1209,
"blockhash" : "000000005b16e489f1e5a192ad505a2a274fe32fd3ed76f6af241d9388ec0cf3",
"blockindex" : 1,
"blocktime" : 1402502132,
"txid" : "5a4f907ee8bbdee7687658894868f7fe3062d339926918c487f6c253f9f4588f",
"time" : 1402502050,
"timereceived" : 1402502050
},
{
"account" : "",
"address" : "mqkHB1kDUWHq6rcaEc9gGKUXEw6JKMF1io",
"category" : "receive",
"amount" : 8256.50000000,
"confirmations" : 826,
"blockhash" : "00000001c4214cbef721c3346937d26714066305c9f7dbfd750951a9879899b0",
"blockindex" : 1,
"blocktime" : 1402560769,
"txid" : "660c62c405ac2fed58ed14def1e65177e6afdb4ab59db5a025e68cd3bebd6bbb",
"time" : 1402560639,
"timereceived" : 1402560639
}
]

remote
IP: 54.209.226.236
remote, just SSH'ed in...

ubuntu@ip-172-31-23-208:~$ darkcoind masternode debug
successfully started masternode
ubuntu@ip-172-31-23-208:~$ darkcoind getinfo
{
"version" : 100913,
"protocolversion" : 70018,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 18959,
"timeoffset" : -24,
"connections" : 20,
"proxy" : "",
"difficulty" : 0.23582818,
"testnet" : true,
"keypoololdest" : 1401955602,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""

http://23.23.186.131:1234/address/mrPbaoAeVVeaiuezEmqs7zQimHHcAtKAqq
Masternode started successfully, yesterday at 10am my local time. So its been 38h with zero payouts.
My other node, 10.9.6, still getting regular payouts. Will update tomorrow to latest version.

I respect variance, except this is clearly not the case.

flare · Jun 13, 2014

yidakee said:
http://23.23.186.131:1234/address/mrPbaoAeVVeaiuezEmqs7zQimHHcAtKAqq
Masternode started successfully, yesterday at 10am my local time. So its been 45h with zero payouts.

My other node, 10.9.6, still getting regular payouts. Will update tomorrow to latest version.

I think i am on the track to find the culprit for the issue you are experiencing - one of my nodes shows as similar behaviour, but i do not yet understand it fully.

Question: The IP you are using now for mrPbao...., did you use it for another adress before (new wallet.dat)?

Keep you posted

chaeplin How do you retrieve the adresses in http://tdrk.poolhash.org/blocks/masterlist.txt ? One of my nodes is getting paid without even being in the list

--> http://tdrk.poolhash.org/blocks/masterlist/18961.txt

Code:

                    ],
    "payee" : "mrG4cTKi1Luewv3WWu8rQfT6mTosTybRS1",
    "masternode_payments" : true
}

EDIT: Got it myself :grin:

Code:

./darkcoind masternode list pubkey
    "184.73.179.148:19999" : "motxZAqgHyaUFQAwM9h6EJHPEVgWumbh8V",

eduffield what happens with a existing IP/vin binding if the wallet.dat is exchanged and new masternodeprivkey (for new wallet + old IP) generated. Is the binding replaced and propagated to the network? mrG4cTKi1Luewv3WWu8rQfT6mTosTybRS1 was bound to adress 184.73.179.148 for several days. Today i created new wallet.dat and new masternodeprivkey and noticed that the old adress is still receiving payments. New key is in masternode list

Code:

./darkcoind masternode list pubkey
    "184.73.179.148:19999" : "motxZAqgHyaUFQAwM9h6EJHPEVgWumbh8V",

yidakee · Jun 13, 2014

flare said:
I think i am on the track to find the culprit for the issue you are experiencing - one of my nodes shows as similar behaviour, but i do not yet understand it fully.

Question: The IP you are using now for mrPbao...., did you use it for another adress before (new wallet.dat)?

Keep you posted

chaeplin How do you retrieve the adresses in http://tdrk.poolhash.org/blocks/masterlist.txt ? One of my nodes is getting paid without even being in the list

--> http://tdrk.poolhash.org/blocks/masterlist/18961.txt

Code:

], "payee" : "mrG4cTKi1Luewv3WWu8rQfT6mTosTybRS1", "masternode_payments" : true }

I am not entirely sure I got your question. So so many upgrades and updates... The remote server IP has been the same for a long while, and so is my local ISP IP. I did generate a new address 0 for new daemon 10.9.13.

A few things I am sure of

a) Remote (or even loca) external IP has not changes in a long while. I do not use Elastic IP.
b) New genkey, 100% sure
c) as a layman in coding, I expect that once listed as :1 that should mean 100% eligibility to get payments. If for some freak reason I am not eligible I should be flagged as :0 and not get payed.

Tomorrow I will stop both my EC2 nodes, so I get a new public IP on start-up. Generate new genkeys and fire it all up again.

flare · Jun 13, 2014

yidakee said:
I am not entirely sure I got your question. So so many upgrades and updates... The remote server IP has been the same for a long while, and so is my local ISP IP. I did generate a new address 0 for new daemon 10.9.13.

Question was basically: Did you ever delete a wallet.dat which was used with the IP and then created a new one?

yidakee · Jun 13, 2014

flare said:
Question was basically: Did you ever delete a wallet.dat which was used with the IP and then created a new one?

To be honest, I'm not sure. It is possible, I remember trashing testnet3 at one time or another. But even still, I do have a valid 1k deposit. Pretty sure my local wallet is "fresh". Actually, yeah, my local wallet is fresh. I had remote Masternode going with 9k, I sent 1k to a new local wallet @ address "0" and the rest to "getnewaddress"

localdarknode@ubuntu:~$ darkcoind listaddressgroupings
[
[
[
"mrPbaoAeVVeaiuezEmqs7zQimHHcAtKAqq",
1000.00000000,
"0"
]
],
[
[
"mqkHB1kDUWHq6rcaEc9gGKUXEw6JKMF1io",
8256.50000000,
""
]
]
]

and local list transactions

localdarknode@ubuntu:~$ darkcoind listtransactions
[
{
"account" : "0",
"address" : "mrPbaoAeVVeaiuezEmqs7zQimHHcAtKAqq",
"category" : "receive",
"amount" : 1000.00000000,
"confirmations" : 1218,
"blockhash" : "000000005b16e489f1e5a192ad505a2a274fe32fd3ed76f6af241d9388ec0cf3",
"blockindex" : 1,
"blocktime" : 1402502132,
"txid" : "5a4f907ee8bbdee7687658894868f7fe3062d339926918c487f6c253f9f4588f",
"time" : 1402502050,
"timereceived" : 1402502050
},
{
"account" : "",
"address" : "mqkHB1kDUWHq6rcaEc9gGKUXEw6JKMF1io",
"category" : "receive",
"amount" : 8256.50000000,
"confirmations" : 835,
"blockhash" : "00000001c4214cbef721c3346937d26714066305c9f7dbfd750951a9879899b0",
"blockindex" : 1,
"blocktime" : 1402560769,
"txid" : "660c62c405ac2fed58ed14def1e65177e6afdb4ab59db5a025e68cd3bebd6bbb",
"time" : 1402560639,
"timereceived" : 1402560639

So yeah, brand new local wallet.
So what do you suggest? Send testnet funds to a new totally unrelated address, trash everything and start clean and fresh?

flare · Jun 13, 2014

yidakee said:
Actually, yeah, my local wallet is fresh. I had remote Masternode going with 9k, I sent 1k to a new local wallet @ address "0" and the rest to "getnewaddress"

Sounds almost like the setup i have, with old address being paid without being in masternodelist and new address not being paid. :grin:

yidakee said:
So yeah, brand new local wallet.
So what do you suggest? Send testnet funds to a new totally unrelated address, trash everything and start clean and fresh?

No suggestions so far, as i need confirmation from Evan - might be a flaw in the masternode protocol.

Workaround currently: new remote IP, new local wallet.dat, new local address 0, new local masternode keygen :smile:

yidakee · Jun 13, 2014

flare said:
Sounds almost like the setup i have, with old address being paid without being in masternodelist and new address not being paid. :grin:

Both nodes seem active, and on the masternode list
My other masternode is also listed as :1 ... its just version 10.9.6.

54.255.159.230:19999 1 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o 1402694299031934 161 354842

Its the new 10.9.13 that does not seem to be getting payed

54.209.226.236:19999 1 mrPbaoAeVVeaiuezEmqs7zQimHHcAtKAqq 1402694061583815 399 126721

flare · Jun 13, 2014

yidakee said:
Both nodes seem active
My other masternode is also listed as :1 ... its just version 10.9.6.

Its the new 10.9.13 that does not seem to be getting payed

Ah ok, then its different to my issue - my node is getting paid without being in the list (neither :1 nor :0)

yidakee · Jun 13, 2014

hmmm... weird indeed.

Ok, tell you what. I'm going to sleep now as I've been working for 14h today and totally knackered. Tomorrow I will send all my tesnet DRK to a new unrelated wallet. Going to nuke the entire local/remote daemons and folders on both local/remote nodes, and start totally fresh on both nodes.

snogcel · Jun 14, 2014

flare said:
Did you generate a new masternode key or reuse the old one when changing the IP?

Had a few minutes today after work to look at this further. Previously I had created a new masternode key from local, and applied it to both remote and local. That didn't work.

Clearing out the testnet3 folder on the remote box (generating a new remote wallet.dat), assigning another IP (remote would not sync - debug.log showed error 4 when connecting to 23.23.186.131), then generating a new MN key from local and applying to both local and remote seemed to clear up the problem. This also removed the old IP (54.187.111.243) out of the masternode list (it was there until I took these steps).

Figured I'd share this info, hopefully this will help with any final fine tuning of the MN system

atavacron · Jun 14, 2014

atavacron said:
I'm home for a about an hour.
I'm going to bring up all of my testnet masternodes. Hopefully nothing out of the ordinary will happen. Lets find out.

Well, I thought I was going to bring them up. A lightning storm took out my Internet. It felt like someone severed a limb.

atavacron · Jun 14, 2014

So let up see. I got 11:21 EST. Time to light 'em up, up, up! :wink:

chaeplin · Jun 14, 2014

I have four nodes in testnet, two for monitoring, 1 for nomp, 1 for masternode(1RC, 3 github).
I will update 4 nodes slowly.

atavacron · Jun 14, 2014

Hmmmm...this is a little odd. I don't recall it taking very long to sync the masternodes. I getting some strange counts (correction no highlight rather the number on the line below the block height).
Are still on version 100913?
It's been about 20min and they do not seem to be increasing to match at some uniform count.

Code:

ip-10-184-98-57.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    54
ip-10-184-96-39.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    53
ip-10-147-244-209.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    49
ip-10-81-135-109.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    67
ip-10-185-221-224.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    9
ip-10-185-196-149.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    53
ip-10-11-150-2.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    60
ip-10-179-16-76.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    67
ip-10-185-218-134.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    53
ip-10-178-47-87.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    53
ip-10-152-159-246.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    53
ip-10-185-168-4.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    3
ip-10-185-246-84.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    52
ip-10-165-51-43.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    67
ip-10-184-98-57.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    54

flare · Jun 14, 2014

atavacron said:

Hmmmm...this is a little odd. I don't recall it taking very long to sync the masternodes. I getting some strange counts (correction no highlight rather the number on the line below the block height).
Are still on version 100913?
It's been about 20min and they do not seem to be increasing to match at some uniform count.

Code:

ip-10-184-98-57.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    54
ip-10-184-96-39.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    53
ip-10-147-244-209.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    49
ip-10-81-135-109.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    67
ip-10-185-221-224.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    9
ip-10-185-196-149.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    53
ip-10-11-150-2.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    60
ip-10-179-16-76.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    67
ip-10-185-218-134.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    53
ip-10-178-47-87.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    53
ip-10-152-159-246.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    53
ip-10-185-168-4.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    3
ip-10-185-246-84.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    52
ip-10-165-51-43.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    67
ip-10-184-98-57.ec2.internal:
        "version" : 100913,
        "protocolversion" : 70018,
        "walletversion" : 60000,
        "blocks" : 19122,
    54

Update to 101001 - it's available on http://www.darkcoin.io/downloads/rc/darkcoind - and save some debug.log files to analyse why they got stuck

chaeplin · Jun 14, 2014

chaeplin said:
I have four nodes in testnet, two for monitoring, 1 for nomp, 1 for masternode(1RC, 3 github).
I will update 4 nodes slowly.

Updated at block 19135 except masternode RC.

atavacron · Jun 14, 2014

flare said:
Update to 101001 - it's available on http://www.darkcoin.io/downloads/rc/darkcoind - and save some debug.log files to analyse why they got stuck

Thanks flare. I'll save the logs for reference.

flare · Jun 14, 2014

yidakee said:
hmmm... weird indeed.

Ok, tell you what. I'm going to sleep now as I've been working for 14h today and totally knackered. Tomorrow I will send all my tesnet DRK to a new unrelated wallet. Going to nuke the entire local/remote daemons and folders on both local/remote nodes, and start totally fresh on both nodes.

Oh joy

Code:

4 mins ago    06/14 07:11:18    16    19160    0.143    152    nomp    mrPbaoAeVVeaiuezEmqs7zQimHHcAtKAqq    30.400

Literally truckloads of love

Code:

4 mins ago    06/14 07:15:42    26    19162    0.139    152    nomp    mrPbaoAeVVeaiuezEmqs7zQimHHcAtKAqq    30.400

atavacron · Jun 14, 2014

atavacron said:
Thanks flare. I'll save the logs for reference.

Ah, much better now.

v0.10.9.x Help test RC2 forking issues

Active member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

snogcel

Guest

Member

Member

Well-known member

Member

Well-known member

Well-known member

Member

Well-known member

Member