v0.10.9.x Help test RC2 forking issues

Status
Not open for further replies.
chaeplin said:
I think this shoud be documented.

"If public ip of masternode is changed, change your masternodeprivkey"
Click to expand...

chaeplin, as I reported earlier, 100% guaranteed, I stopped EC2 Instance to generate new external IP. Updated local and remote with brand new masternoprivkey. The only thing that did not change was the local wallet with the 1k deposit.

I have received 2 payouts, since updating. Last one was at block 19315, about 3 hours ago. Something is up with your list my friend.
Working today, very busy, so maybe later I will update to 10.10.1, and a new masternodeprivkey, new IP and new wallet.
 
yidakee said:
chaeplin, as I reported earlier, 100% guaranteed, I stopped EC2 Instance to generate new external IP. Updated local and remote with brand new masternoprivkey. The only thing that did not change was the local wallet with the 1k deposit.

I have received 2 payouts, since updating. Last one was at block 19315, about 3 hours ago. Something is up with your list my friend.
Working today, very busy, so maybe later I will update to 10.10.1, and a new masternodeprivkey, new IP and new wallet.
Click to expand...
Here is update list of moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o http://tdrk.poolhash.org/blocks/masterlist/moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o.txt

Got paid at 19315 with flag 1. And I have updated my node at 19135.

Code: 
19313.txt:54.255.159.230:19999 1 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o 1402744409328805 2009 404953
19314.txt:54.255.159.230:19999 1 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o 1402744409328805 2019 404953
19314.txt: "payee" : "moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o",
19315.txt:54.255.159.230:19999 1 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o 1402744409328805 2025 404953
19316.txt:54.255.159.230:19999 1 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o 1402744409328805 2072 404953
19317.txt:54.255.159.230:19999 0 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o 1402744409328805 3919 404953
19318.txt:54.255.159.230:19999 0 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o 1402744409328805 3974 404953

If you changed masternodeprivkey and ip, might be version issue.
Code: 
ubuntu@ip-172-31-4-239:~$ darkcoind getinfo
{
    "version" : 91001,

Here is 3 node result of query. new ip not listed, old one is flag zerod.
Code: 
darktest@sv1:/dev/shm/darktest/masterlist> darkcoind masternode list | grep 54.254.205.57

darktest@sv1:/dev/shm/darktest/masterlist> darkcoind masternode list pubkey | grep moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o

    "54.255.159.230:19999" : "moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o",
darktest@sv1:/dev/shm/darktest/masterlist> darkcoind masternode list | grep 54.255.159.230

    "54.255.159.230:19999" : 0,
Code: 
: restarted
user@sv2:~> darkcoind masternode list | grep 54.254.205.57

user@sv2:~>

user@sv2:~> darkcoind masternode list pubkey | grep moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o

user@sv2:~>
Code: 
ubuntu@ip-172-31-4-239:~$ darkcoind masternode list | grep 54.254.205.57

ubuntu@ip-172-31-4-239:~$

ubuntu@ip-172-31-4-239:~$ darkcoind masternode list pubkey | grep moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o

    "54.255.159.230:19999" : "[B]moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o[/B]",
ubuntu@ip-172-31-4-239:~$ darkcoind masternode list | grep 54.255.159.230

    "54.255.159.230:19999" : 0,

ubuntu@ip-172-31-4-239:~$
[c/ode]
 
Exactly! Very strange indeed. Doesnt matter though, could be a version bug. Will update ASAP clean slate and report back.
 
MykelSIlver said:
Is it possible to setup a HOT only masternode (on MainNet 9999)?
When I setup a HOT only masternode starting my masternode returns the message:
"inbound port is not open. Please open it and try again. (19999 for testnet and 9999 for mainnet)"

I 'm 100% sure I have the TCP/UDP port 9999 open

Any suggestions what might be the case?
Thanks in advance
Click to expand...

Anyone?
 
Hi all, Thanks for all the help.

Just got my masternode running but when I type darkcoind getinfo on local and ec2 sever I get

"version" : 100913,
"protocolversion" : 70018,
"walletversion" : 60000,
"balance" : 2000.00000000,
"blocks" : 18979,
"timeoffset" : 0,
"connections" : 1,
"proxy" : "",
"difficulty" : 0.18024968,
"testnet" : true,
"keypoololdest" : 1402590710,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""

Should the blocks match

http://23.23.186.131:1234/chain/Dark

The site is on 19378








Mine is on "blocks" : 18979

also I keep getting broken pipe and losing connection not sure if its something to do with my iptables
#-----
*filter
:INPUT ACCEPT [1038:145425]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [434:87191]
-A INPUT -i eth0 -p tcp -m tcp --dport 9998 -j REJECT --reject-with tcp-reset
-A INPUT -i eth0 -p tcp -m tcp --dport 9999 --tcp-flags FIN,SYN,RST,ACK SYN -m connlimit --connlimit-above 8 --connlimit-mask 24 --connlimit-saddr -j REJECT --reject-with tcp-reset
-A INPUT -i eth0 -p tcp -m tcp --dport 9999 --tcp-flags FIN,SYN,RST,ACK SYN -m connlimit --connlimit-above 2 --connlimit-mask 32 --connlimit-saddr -j REJECT --reject-with tcp-reset
-A INPUT -i eth0 -p tcp -m conntrack --ctstate NEW -m tcp --dport 9999 -j ACCEPT
-A INPUT -i eth0 -p tcp -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9999 -m conntrack --ctstate NEW -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9999 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 9999 -j ACCEPT
-A OUTPUT -o eth0 -j ACCEPT
COMMIT
#-----

should I change eth0 to wlan0 since i am using wifi also should I change 9999 to 19999 since we are testnet ????

Thanks all
 
MykelSIlver said:
Anyone?
Click to expand...

I don't know, it might be related to my problem. I'm trying to do a remote, but my local can't see the remote ip address (and possibly nobody else either) I'm using amazon ec2 tiny, I've set it up with Mr. President's instructions (only using port 19999 for testnet) and last night before going to sleep, I tried one last time by changing my elastic IP address (but didn't change masternodekey, which I'll try next).

Anyway, all issues point to a closed port, even so I should have port 19999 open by all accounts on both machines. Right now, I'm going to change the Masternodekey and open all ports in my EC2 to see if it helps. I was just too tired to continue yesterday (Son Graduated High School, YAAAAY!) Big day!
 
Well, I flushed my ip tables, I opened all ports, I created a new masternodekey, I waited 10 minutes to see if my remote ip address would show up on my local machine with ./darkcoind getpeerinfo (many others do) but it didn't show up, so I tried masternode start on my local, to see what would happen, and it started and listed on my home IP address, and not on the remote ip address. I'm so at a loss, it's not funny! BTW, after flusing and opening all ports in security groups I even rebooted the remote, but to no avail. There must be something super stupid that I'm doing? BTW, I also specifically opened port 19999 for my local machine on my router as well.

Remote config:
Code: 
rpcuser=Me
rpcpassword=la;iueljraalkdfOIU(UOIJPIOTY*()*)*_(IIjkaruoUOjfera
listen=1
server=1
daemon=1
logtimestamps=1
masternode=1
masternodeprivkey=93KcsUbqovHzXU5asV8D6bpBpYE7VDr7GW7YgTe1prdXAPDzvN8
addnode=23.23.186.131:19999
testnet=1
maxconnections=256

Local
Code: 
rpcuser=Me
rpcpassword=la;iueljraalkdfOIUUOIJPIOTY***IIjkaruoUOjfera
addnode=23.23.186.131:19999
addnode=54.183.68.222:19999
testnet=1
maxconnections=256
masternodeprivkey=93KcsUbqovHzXU5asV8D6bpBpYE7VDr7GW7YgTe1prdXAPDzvN8
masternode=1
masternodeaddr=54.183.68.222:19999

Is nobody else having this problem? If not, it must be me, and I just can't see the tree for the forest!

My remote (amazon) IP address doesn't show up in the debug log nor the local one.
 
Last edited by a moderator:
Vote system is behaving quite nice, vote queue ist starting to stack up:

Code: 
Blockheight    Pubkey    Votes
19449    VA1mAwW42aTQ5Ubj2yEuELcUSNDvCtz27    5
19450    Z92SLSwb3z2D47g47Y1E9LczimJiVFtvv    4
19451    d3PjFPF8xRR5J6RJSjeWgmm6dyDg2YCC4    3
19452    fqgi8JuLcrrnhkw1JnoCFNqV7qPQSQ85f    2
19453    cBWcZChK3YzEsrNfUmBQnDkizvq6oUDYJ    1

As a side effect we can expect paid blocks to be 100% from now :smile:

What will be interesting to see: What will happen if the queue is filled to size 10: Will voting algorithm start to incorrectly remove fully confirmed votes (5 confirmation) due to expiration, or will the queue length continue to grow (11..12..13.. infinity)

We will see the next days :smile:
 
TanteStefana said:
Well, I flushed my ip tables, I opened all ports, I created a new masternodekey, I waited 10 minutes to see if my remote ip address would show up on my local machine with ./darkcoind getpeerinfo (many others do) but it didn't show up, so I tried masternode start on my local, to see what would happen, and it started and listed on my home IP address, and not on the remote ip address. I'm so at a loss, it's not funny! BTW, after flusing and opening all ports in security groups I even rebooted the remote, but to no avail. There must be something super stupid that I'm doing? BTW, I also specifically opened port 19999 for my local machine on my router as well.

Remote config:
Code: 
rpcuser=Me
rpcpassword=la;iueljraalkdfOIU(UOIJPIOTY*()*)*_(IIjkaruoUOjfera
listen=1
server=1
daemon=1
logtimestamps=1
masternode=1
masternodeprivkey=93KcsUbqovHzXU5asV8D6bpBpYE7VDr7GW7YgTe1prdXAPDzvN8
addnode=23.23.186.131:19999
testnet=1
maxconnections=256

Local
Code: 
rpcuser=Me
rpcpassword=la;iueljraalkdfOIUUOIJPIOTY***IIjkaruoUOjfera
addnode=23.23.186.131:19999
addnode=54.183.68.222:19999
testnet=1
maxconnections=256
masternodeprivkey=93KcsUbqovHzXU5asV8D6bpBpYE7VDr7GW7YgTe1prdXAPDzvN8
masternode=1
masternodeaddr=54.183.68.222:19999

Is nobody else having this problem? If not, it must be me, and I just can't see the tree for the forest!

My remote (amazon) IP address doesn't show up in the debug log nor the local one.
Click to expand...

Are you using Elastic IP with Amazon? If so be sure to Associate that IP with your instance - that stupid mistake drove me nuts for a couple days :)
 
snogcel said:
Are you using Elastic IP with Amazon? If so be sure to Associate that IP with your instance - that stupid mistake drove me nuts for a couple days :)
Click to expand...

Simple check for that: does
Code: 
ubuntu@ip-10-180-220-117:~$ curl icanhazip.com
54.224.80.160

on the remote server return the IP you are expecting?
 
flare said:
Vote system is behaving quite nice, vote queue ist starting to stack up:

Code: 
Blockheight    Pubkey    Votes
19449    VA1mAwW42aTQ5Ubj2yEuELcUSNDvCtz27    5
19450    Z92SLSwb3z2D47g47Y1E9LczimJiVFtvv    4
19451    d3PjFPF8xRR5J6RJSjeWgmm6dyDg2YCC4    3
19452    fqgi8JuLcrrnhkw1JnoCFNqV7qPQSQ85f    2
19453    cBWcZChK3YzEsrNfUmBQnDkizvq6oUDYJ    1

As a side effect we can expect paid blocks to be 100% from now :smile:

What will be interesting to see: What will happen if the queue is filled to size 10: Will voting algorithm start to incorrectly remove fully confirmed votes (5 confirmation) due to expiration, or will the queue length continue to grow (11..12..13.. infinity)

We will see the next days :smile:
Click to expand...

In your opinion what do you feel the "ramp up" time is for the Masternode network voting system? My understanding is that this voting system is accumulating votes in mainnet, and I'd like to move my node there ahead of the hard fork but curious how far ahead of time this should take place
 
snogcel said:
In your opinion what do you feel the "ramp up" time is for the Masternode network voting system? My understanding is that this voting system is accumulating votes in mainnet, and I'd like to move my node there ahead of the hard fork but curious how far ahead of time this should take place
Click to expand...

There is no accumulation of votes before payout starts. The first block after payment start will contain one vote, the second block two votes and so on.

Code: 
Block 100000

Blockheight    Pubkey    Votes
100000    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    1

======================

Block 100001


Blockheight    Pubkey    Votes
100000    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    2
100001    yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy    1

So there is no benefit in joining early to the masternetwork (beside checking all is working). As long as your IP/address is propagated to the network, all miners will potentially vote for your node - depending on result of pseudo random number generator. This scoring is like rolling the dice: The past results do not matter, they are independed.

To be on the safe side join the network 1 hour before payment start, propagation usually takes no more than 2-3 minutes (compare the graph when atavacron simultaneously started his 50 nodes in testnet, they all got listed in no time)
 
Last edited by a moderator:
flare said:
Simple check for that: does
Code: 
ubuntu@ip-10-180-220-117:~$ curl icanhazip.com
54.224.80.160

on the remote server return the IP you are expecting?
Click to expand...
yup:
Code: 
ubuntu@ip-172-31-8-1:~$ curl icanhazip.com
54.183.68.222

And yes, it's an elastic IP. Wow, it's gotta be so big and plain as the nose on my face, 'cause I totally can't see it!
 
flare said:
There is no accumulation of votes before payout starts. The first block after payment start will contain one vote, the second block two votes and so on.
Code: 
Block 100000

Blockheight    Pubkey    Votes
100000    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    1

======================

Block 100001


Blockheight    Pubkey    Votes
100000    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    2
100001    yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy    1

So there is no benefit in joining early to the masternetwork (beside checking all is working). As long as your IP/address is propagated to the network, all miners will potentially vote for your node -depending on result of random generator.

To be on the safe side join the network 1 hour before payment start, propagation usually takes no more than 2-3 minutes (compare the graph when atavacron start his 50 nodes in testnet, they all get listed in no time)
Click to expand...

Thanks for the great explanation! Really appreciate the insights on top of all the QA you've been doing :)
 
TanteStefana said:
yup:
Code: 
ubuntu@ip-172-31-8-1:~$ curl icanhazip.com
54.183.68.222

And yes, it's an elastic IP. Wow, it's gotta be so big and plain as the nose on my face, 'cause I totally can't see it!
Click to expand...

Perhaps try clearing the testnet3 folder entirely and generating a new wallet addr for the remote? I'd also strongly suggest running a 2nd terminal window on remote and local machines using the "tail -f debug.log" command to see what's going on under the hood
 
Ok, gonna try from true scratch (except I'm going to keep my IP addresses...)

Oh wow, stupid #1, last night I updated darkcoind on both machines but managed to download 10.9.13 for my remote! I didn't realize it wasn't updating, though it did receive a payment 'cause I tried to make it a masternode without a remote wallet. Didn't even get that far, LOL 'cause I realized I had the wrong version. I knew it was going to be something super stupid! I'm still not out of the woods, I need to make this work. But, I'm going to take a break from this for a bit so I don't make so many brain farts!

Thank you guys for helping me. It's unfortunate that one can't help a person who does such monumentally basic mistakes, LOL. Too many to try to hit! I hope I don't come back with more sob stories of how I can't get this to work. In fact, I'll try not to even if I'm still stuck, it'll probably eventually come to me :tongue:
 
Last edited by a moderator:
Ok, so I

- stopped/started EC2 Instance to generate new external IP
- trashed testnet3 on both local machines (so to generate brand new wallet address 0)
- updated everything to 10.10.1
- generated new masternodeprivkey
- successfully started masternodes.

Now for the weird stuff.

MN1 - EC2 North Virginia - 54.88.23.198 - Shows up instantly on chaeplin's list as :1 ... but remote daemon reports it twice (!!) - local daemon reports just once.
address 0 ;
mpv3jJQi9otaVTDhheHyKP7k8toLd73ott
ubuntu@ip-172-31-23-208:~$ darkcoind masternode list | grep 198
"54.198.191.99:19999" : 1,
"54.198.109.108:19999" : 1,
"54.198.145.174:19999" : 1,
"54.198.252.150:19999" : 1,
"54.88.23.198:19999" : 1,
"54.88.23.198:19999" : 1
Click to expand...

MN2 - EC2 Singapore - 54.255.178.13 - does not show up on chaeplin's list - local and remote daemon cannot find it either!
address 0
mvdVPpgaLxZGv1ddWTKeAsELc7uxAhHuZ6
ubuntu@ip-172-31-23-208:~$ darkcoind masternode list | grep 13
"54.197.213.80:19999" : 1,
"54.80.186.130:19999" : 1,
"107.21.138.152:19999" : 1,
"54.224.28.113:19999" : 1,
"23.22.13.31:19999" : 1,
"54.242.139.236:19999" : 1,
"50.16.13.19:19999" : 1,
"54.178.139.242:19999" : 1,
Click to expand...

All debugs report "successfully started masternode" - I suspect something funky on Singapore servers

I know its been only like 5 minutes since I've fired up the nodes, but it seems to me that Amazon Singapore is not a very good zone. SSH lags like a bitch. Will let it roll for now, see what happens.
 
Last edited by a moderator:
TanteStefana said:
I don't know, it might be related to my problem. I'm trying to do a remote, but my local can't see the remote ip address (and possibly nobody else either) I'm using amazon ec2 tiny, I've set it up with Mr. President's instructions (only using port 19999 for testnet) and last night before going to sleep, I tried one last time by changing my elastic IP address (but didn't change masternodekey, which I'll try next).

Anyway, all issues point to a closed port, even so I should have port 19999 open by all accounts on both machines. Right now, I'm going to change the Masternodekey and open all ports in my EC2 to see if it helps. I was just too tired to continue yesterday (Son Graduated High School, YAAAAY!) Big day!
Click to expand...

I have this issue on my local machine. All my ports are open for 100% sure. Even with this port widely open this "inbound port is not open. Please open it and try again. (19999 for testnet and 9999 for mainnet)" message occurs. Really weird that no one else complains about this... Hope to read more about it...
 
Well, as you can see above, I had a brain fart and ended up downloading the wrong "update" and simply reinstalled 10.9.13 so it wasn't connectin' to nothin'
I never got the "inbound port is not open" error, unfortunately. Is your local machine a windows or Linux/unix?

Also, is anyone spending their coin in their off line wallet? I'd like to know if the system catches it right away? Got to go for a bit, will be back later. Hopefully I'll get it working then and then I want to try spending my coins and see what happens :D
 
Status
Not open for further replies.
Back
Top