v0.10.9.x Help test RC2 forking issues

jimbit · Jun 11, 2014

snogcel said:
Hey guys,

I'd like to help out the testing process by running a testnet MasterNode - can anyone send 1000 drk to XqUeH6armeKnXyoykvEyWGWaoLaxFwoM2o ?

nice try, looks like a real address?

darkcoind sendtoaddress XqUeH6armeKnXyoykvEyWGWaoLaxFwoM2o 1100
error: {"code":-5,"message":"Invalid DarkCoin address"}

eduffield · Jun 11, 2014

***** MASTERNODES PLEASE UPDATE TO 10.9.12 ******

Added local port checking to make sure it's open :grin:

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

snogcel · Jun 11, 2014

jimbit said:
nice try, looks like a real address?

Realized shortly after posting that I was being an idiot

- Chaeplin sent over 1000drk to a testnet address I posted (moSakqDHKv1BJwfTeJsEVJzVYTWeycHRaH), but for some reason I'm still not seeing it:

Code:

{
    "version" : 100911,
    "protocolversion" : 70018,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 17416,
    "timeoffset" : 1,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.20180760,
    "testnet" : true,
    "keypoololdest" : 1402447671,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
}

Any ideas on what I'm doing wrong?

jimbit · Jun 11, 2014

Updated...

Code:

2014-06-11 01:19:20 send version message: version 70018, blocks=17416, us=54.203.217.224:19999, them=104.33.210.231:19999, peer=104.33.210.231:19999

"version" : 100912,
  "protocolversion" : 70018,
  "walletversion" : 60000,
  "balance" : 7330.72629998,
  "blocks" : 17416,
  "timeoffset" : 0,
  "connections" : 7,
  "proxy" : "",
  "difficulty" : 0.20180760,
  "testnet" : true,
  "keypoololdest" : 1401626368,
  "keypoolsize" : 99,
  "paytxfee" : 0.00000000,
  "mininput" : 0.00001000,
  "unlocked_until" : 0,
  "errors" : ""
}
ubuntu@ip-10-252-204-115:~/.darkcoin$ darkcoind masternode list
{
  "184.73.179.148:19999" : 1,
  "184.73.179.187:19999" : 1,
  "188.226.248.36:19999" : 1,
  "37.187.47.129:19999" : 1,
  "54.203.217.224:19999" : 1,
  "54.86.103.191:19999" : 1,
  "84.25.161.117:19999" : 1,
  "54.255.159.230:19999" : 1,
  "184.73.179.196:19999" : 1,
  "23.242.106.27:19999" : 1,
  "54.76.47.232:19999" : 1,
  "188.226.243.116:19999" : 1,
  "98.165.130.67:19999" : 1,
  "107.170.200.102:19999" : 1,
  "87.230.94.57:19999" : 1

snogcel · Jun 11, 2014

chaeplin said:
Nothing, testnet need more hashing power.
In block 17416, almost one hour.
Wait a little longer.

Cool thanks

eduffield · Jun 11, 2014

chaeplin said:

Code:

2014-06-11 01:29:31 CheckBlock(): matchingVoteRecords 3
2014-06-11 01:29:31 CheckBlock(): badVote 0
2014-06-11 01:29:31 CheckBlock(): foundMasterNodePayment 0
2014-06-11 01:29:31 CheckBlock(): removedMasterNodePayments 0
2014-06-11 01:29:31 CheckBlock():       17414     2MwufYmioyzKp6zRztpe6zCZL9pNYRv8f5b         4
2014-06-11 01:29:31 CheckBlock():       17415     2N8Eyrfd9JvoP6tyKeJf2WZCtcgGf1X7d2T         3
2014-06-11 01:29:31 CheckBlock():       17416     2N3YeagkFkEHP95kc5mzG8pYGNuVdYGqWkQ         2
2014-06-11 01:29:31 CheckBlock():       17417     2N8Eyrfd9JvoP6tyKeJf2WZCtcgGf1X7d2T         1
2014-06-11 01:29:31 ERROR: CheckBlock() : Missing masternode votes
2014-06-11 01:29:31 ERROR: ProcessBlock() : CheckBlock FAILED

hmmm

Looking into it

Edit: It looks like it got past it. That was a glitch though, are we all on the same block now?

jimbit · Jun 11, 2014

could someone please explain to me how I can figure out what my hash is for the voting.

darkcoind masternode votes
{
"17418" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG"
}

darkcoind masternode votes
{
"17418" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
"17419" : "OP_DUP OP_HASH160 60888d5ae7c84c8a4c11c8001a75591cb3d944ed OP_EQUALVERIFY OP_CHECKSIG",
"17420" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
"17421" : "OP_DUP OP_HASH160 b27ad157bd495c98eebfb588cc071c7be6f7ad37 OP_EQUALVERIFY OP_CHECKSIG"
}

jimbit · Jun 11, 2014

How can I have a vote for a block that is not found yet? 17429

{
"17420" : "OP_DUP OP_HASH160 aa09e4b6969c00f9e3ba46dc5da62241c525d180 OP_EQUALVERIFY OP_CHECKSIG",
"17421" : "OP_DUP OP_HASH160 b27ad157bd495c98eebfb588cc071c7be6f7ad37 OP_EQUALVERIFY OP_CHECKSIG",
"17422" : "OP_DUP OP_HASH160 60888d5ae7c84c8a4c11c8001a75591cb3d944ed OP_EQUALVERIFY OP_CHECKSIG",
"17423" : "OP_DUP OP_HASH160 5b52346725796db95b833a6ef7a3d3576645b451 OP_EQUALVERIFY OP_CHECKSIG",
"17424" : "OP_DUP OP_HASH160 4aa9f48fc2153ab8e0dd56cc20b42792ae7ac8a4 OP_EQUALVERIFY OP_CHECKSIG",
"17425" : "OP_DUP OP_HASH160 657d9a4ae40b3f1685c4e7c1e8060afbed55657c OP_EQUALVERIFY OP_CHECKSIG",
"17426" : "OP_DUP OP_HASH160 21749baf12b74727756d03158a4c72457dd76f74 OP_EQUALVERIFY OP_CHECKSIG",
"17427" : "OP_DUP OP_HASH160 657d9a4ae40b3f1685c4e7c1e8060afbed55657c OP_EQUALVERIFY OP_CHECKSIG",
"17428" : "OP_DUP OP_HASH160 23ad6303f7d626b7040b969349c0db9612709345 OP_EQUALVERIFY OP_CHECKSIG",
"17429" : "OP_DUP OP_HASH160 657d9a4ae40b3f1685c4e7c1e8060afbed55657c OP_EQUALVERIFY OP_CHECKSIG"
}
ubuntu@ip-10-252-204-115:~/.darkcoin$ darkcoind getinfo
{
"version" : 100912,
"protocolversion" : 70018,
"walletversion" : 60000,
"balance" : 7330.72629998,
"blocks" : 17428,
"timeoffset" : 0,
"connections" : 8,
"proxy" : "",
"difficulty" : 0.06033953,
"testnet" : true,
"keypoololdest" : 1401626368,
"keypoolsize" : 99,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""

jimbit · Jun 11, 2014

chaeplin said:
masternode votes shows vote for next block.

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

thanks..

Can you tell me how to determine what my voting hash is for a particular MN please.

jimbit · Jun 11, 2014

chaeplin said:
https://github.com/darkcoinproject/darkcoin/blob/forkfix/src/rpcdarksend.cpp#L84

It's like pubkey of NM.

EDIT:
https://github.com/darkcoinproject/darkcoin/blob/forkfix/src/rpcdarksend.cpp#L35
"list supports 'active', 'vin', 'pubkey', 'lastseen', 'activeseconds'\n");

thank you...

chaeplin · Jun 11, 2014

jimbit said:
thank you...

I don't know exactly. ;D I just check the src.

chaeplin · Jun 11, 2014

eduffield said:
***** MASTERNODES PLEASE UPDATE TO 10.9.12 ******

Added local port checking to make sure it's open :grin:

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

bump

eduffield · Jun 11, 2014

It looks like the glitch earlier was caused by the daemon doing a rescan of the last couple hundred blocks. I suppose I need to keep track of the last best block myself instead of using pindexBest. I'll implement that in the morning!

archLinuxUser · Jun 11, 2014

eduffield said:
***** MASTERNODES PLEASE UPDATE TO 10.9.12 ******

Added local port checking to make sure it's open :grin:

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

I think this is awesome, but is it possible to put into code to ban MN's that are not reachable on port 19999 (if testnet) or 9999 (if mainnet)? These MN's would not be providing a POS and does not need to be part of the MN list or as a voter.

The binary will probably succeed on connecting to my local port due to the same binary having a listener on 19999 (testnet) but if I didn't open/portforward for 19999 on my ddwrt router, then I'm not providing MN POS (as flare has mentioned).

Apologies if this is in the plan for a future version...

Thank you!

chaeplin · Jun 11, 2014

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

Code:

Current time: 1402456381
ip status address lastseen sec(ago) activeseconds
107.20.28.12:19999 1 n2eL7u3pgqMYNSxVbvHDTL1WJJzS92qUbU 1402455692189700 688 115718

snogcel · Jun 11, 2014

Any thoughts on why the following firewall config is not allowing my MN to connect?

Code:

# Generated by iptables-save v1.4.21 on Tue Jun 10 21:34:33 2014
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [103:15380]
:TCP - [0:0]
:UDP - [0:0]
-A INPUT -s 10.0.0.167/32 -i wlp1s0 -p tcp -m tcp --dport 55221 -j ACCEPT
-A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m conntrack --ctstate INVALID -j DROP
-A INPUT -p icmp -m icmp --icmp-type 8 -m conntrack --ctstate NEW -j ACCEPT
-A INPUT -p udp -m conntrack --ctstate NEW -j UDP
-A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -m conntrack --ctstate NEW -j TCP
-A INPUT -p udp -j REJECT --reject-with icmp-port-unreachable
-A INPUT -p tcp -j REJECT --reject-with tcp-reset
-A INPUT -j REJECT --reject-with icmp-proto-unreachable
-A TCP -p tcp --dport 19999 -j ACCEPT
-A TCP -p tcp --dport 19998 -j ACCEPT
-A TCP -p tcp --dport 9999 -j ACCEPT
-A TCP -p tcp --dport 9998 -j ACCEPT
COMMIT
# Completed on Tue Jun 10 21:34:33 2014

darkcoind seems to be speaking with the net no problems:

Code:

{
    "version" : 100912,
    "protocolversion" : 70018,
    "walletversion" : 60000,
    "balance" : 2000.00000000,
    "blocks" : 17494,
    "timeoffset" : 1,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.29036717,
    "testnet" : true,
    "keypoololdest" : 1402447671,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
}

However, when I attempt to masternode start I get the following: inbound port is not open. Please open it and try again. (19999 for testnet and 9999 for mainnet)

chaeplin · Jun 11, 2014

snogcel said:

Any thoughts on why the following firewall config is not allowing my MN to connect?

Code:

# Generated by iptables-save v1.4.21 on Tue Jun 10 21:34:33 2014
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [103:15380]
:TCP - [0:0]
:UDP - [0:0]
-A INPUT -s 10.0.0.167/32 -i wlp1s0 -p tcp -m tcp --dport 55221 -j ACCEPT
-A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m conntrack --ctstate INVALID -j DROP
-A INPUT -p icmp -m icmp --icmp-type 8 -m conntrack --ctstate NEW -j ACCEPT
-A INPUT -p udp -m conntrack --ctstate NEW -j UDP
-A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -m conntrack --ctstate NEW -j TCP
-A INPUT -p udp -j REJECT --reject-with icmp-port-unreachable
-A INPUT -p tcp -j REJECT --reject-with tcp-reset
-A INPUT -j REJECT --reject-with icmp-proto-unreachable
-A TCP -p tcp --dport 19999 -j ACCEPT
-A TCP -p tcp --dport 19998 -j ACCEPT
-A TCP -p tcp --dport 9999 -j ACCEPT
-A TCP -p tcp --dport 9998 -j ACCEPT
COMMIT
# Completed on Tue Jun 10 21:34:33 2014

darkcoind seems to be speaking with the net no problems:

Code:

{
    "version" : 100912,
    "protocolversion" : 70018,
    "walletversion" : 60000,
    "balance" : 2000.00000000,
    "blocks" : 17494,
    "timeoffset" : 1,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.29036717,
    "testnet" : true,
    "keypoololdest" : 1402447671,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
}

However, when I attempt to masternode start I get the following: inbound port is not open. Please open it and try again. (19999 for testnet and 9999 for mainnet)

First deny 19998, 9998 from outside. It's for rpc port.

I can't find any porblem from your iptables config.

If your machine is in private ip address network,
you need port forwarding 9999/19999 from outside to your machine ip 9999/19999 at router.

snogcel · Jun 11, 2014

chaeplin said:
First deny 19998, 9998 from outside. It's for rpc port.

I can't find any porblem from your iptables config.

Is your machine using wifi ?
And Is your machine using a private ip address ?

You need port forwarding 9999/19999 from outside to your machine ip 9999/19999 at router.

Thanks - I cut out the 9998 and 19998 entries in my iptables config. To answer your question this machine is using wifi and has been assigned a static ip in my home network. I've double checked my port forwarding and 19999 and 9999 are being routed to this box.

archLinuxUser · Jun 11, 2014

snogcel said:
Thanks - I cut out the 9998 and 19998 entries in my iptables config. To answer your question this machine is using wifi and has been assigned a static ip in my home network. I've double checked my port forwarding and 19999 and 9999 are being routed to this box.

Can't you stop iptables and try to start masternode? To see if it's iptables that's causing the problems. I don't know if you have "valuables" on this box and can't run the risk for a few minutes.

I made a typo on my darkcoin.conf on the port (put 9999 instead of 19999) and couldn't start my masternode on testnet.

Is it possible another application has already a hold of port 19999?

Code:

netstat -tulanp | grep 0:19999

chaeplin · Jun 11, 2014

snogcel said:
Thanks - I cut out the 9998 and 19998 entries in my iptables config. To answer your question this machine is using wifi and has been assigned a static ip in my home network. I've double checked my port forwarding and 19999 and 9999 are being routed to this box.

There is no deny or reject before COMMIT.
So your iptables is opened from outside.

~~The iptables is intended to use at EC2 with Security-group(a fire-wall, only open 22, 9999, deny all).~~

Oh I have found -J TCP.

Looks good.

EDIT: What is default behaviour of jump statement at last ? RETURN ?
-A TCP -j RETURN

-j DENY can be replaced to -j REJECT --reject-with tcp-reset or -j DROP

eduffield I think port checking might have a problem in NAT environment.

v0.10.9.x Help test RC2 forking issues

Active member

Core Developer

snogcel

Guest

Active member

snogcel

Guest

Core Developer

Active member

Active member

Active member

Active member

Well-known member

Well-known member

Core Developer

New member

Well-known member

snogcel

Guest

Well-known member

snogcel

Guest

New member

Well-known member