• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Darkcoin Update / Masternode requirements / Masternode Payments

Status
Not open for further replies.
https://bitcointalk.org/index.php?topic=421615.msg6206936#msg6206936

I have duplicate master node entry.
Code:
ubuntu@ip:~/.darkcoin$ darkcoind masternode list 
{
    "23.23.186.131:9999" : 1,
    "54.213.217.28:9999" : 1,
    "54.238.156.138:9999" : 1,
    "87.242.50.175:9999" : 1,
    "112.175.123.94:9999" : 1,
    "94.23.22.195:9999" : 1,
    "142.161.23.40:9999" : 1,
    "54.193.124.32:9999" : 1,
    "54.193.127.186:9999" : 1,
    "98.101.247.254:9999" : 1,
    "95.85.59.159:9999" : 1,
    "54.86.15.235:9999" : 1,
    "212.101.16.116:9999" : 1,
    "98.176.239.187:9999" : 1,
    "54.193.127.186:9999" : 1
}

54.193.127.186 is my ec2 t1.micro instance.

Restart darkcoind dosn't help.
I have changed EC2 Public IP Address to EC2 Elastic IP Address, duplicate gone.
(darkcoind stoped, config changed)
I don't know why.
 
I had that too, the 1 was a 0 though and when I updated the wallet to the latest beta today, it stopped happening. I got no real info for you, just solidarity, LOL
 
Which one is the latest beta by the way, github branch master HEAD? I tried the develop branch but that one is really outdated...
 
Code:
./darkcoind-prop -daemon -server && tail -f ~/.darkcoin/debug.log
./darkcoind-prop: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./darkcoind-prop)
./darkcoind-prop: /lib/libc.so.6: version `GLIBC_2.15' not found (required by ./darkcoind-prop)
./darkcoind-prop: /lib/libc.so.6: version `GLIBC_2.14' not found (required by ./darkcoind-prop)

meh!
 
Code:
./darkcoind-prop -daemon -server && tail -f ~/.darkcoin/debug.log
./darkcoind-prop: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./darkcoind-prop)
./darkcoind-prop: /lib/libc.so.6: version `GLIBC_2.15' not found (required by ./darkcoind-prop)
./darkcoind-prop: /lib/libc.so.6: version `GLIBC_2.14' not found (required by ./darkcoind-prop)

meh!

meh!!!. Debian ??!!. have to wait.
DarkSend is in beta stage.
 
Question on Masternode list.

Does Masternode has cache time for Masternode list ?

When doing 'darkcoind masternode list', it still show 54.193.127.186.
54.193.127.186 is my old t1.micro's changed two days ago.
 
Are there any recommendation on protecting the masternode server? Specifically mitigating a DDOS attack. I know protection is up to server owner but just wanted to see if their are any recommendations.
 
I would really like to help support the network and run a node, but myself and other users may need some extra advice to walk through it or the process comes across as too technically challenging. Would anyone care to walk us through it, links included?
 
Hi,

My masternode stopped connecting to other nodes.
Was there any update to the daemon that I'm not aware of?
Thanks.

Before daemon restart:
Code:
{ "54.213.217.28:9999" : 0, "23.23.186.131:9999" : 0, "54.238.156.138:9999" : 0, "87.242.50.175:9999" : 0, "112.175.123.94:9999" : 0, "94.23.22.195:9999" : 0, "142.161.23.40:9999" : 0, "54.193.124.32:9999" : 0, "54.193.127.186:9999" : 0, "98.101.247.254:9999" : 0, "95.85.59.159:9999" : 0, "54.86.15.235:9999" : 0, "212.101.16.116:9999" : 0, "98.176.239.187:9999" : 0, "54.85.112.223:9999" : 0, "107.170.15.238:9999" : 0, "176.31.113.167:9999" : 0, "141.255.184.191:9999" : 0, "162.243.234.7:9999" : 0, "54.245.240.204:9999" : 0 }

After:
Code:
{
    "54.213.217.28:9999" : 0
}
It was running great for the last 4 days....

Some log:
Code:
2014-04-17 13:15:50 accepted connection 77.173.163.153:36190
2014-04-17 13:15:50 partner 77.173.163.153:36190 using obsolete version 60002; d
isconnecting
2014-04-17 13:15:50 ProcessMessage(version, 100 bytes) FAILED
2014-04-17 13:15:50 disconnecting node 77.173.163.153:36190
2014-04-17 13:15:53 RegisterAsMasterNode
2014-04-17 13:15:54 received getdata (226 invsz)
2014-04-17 13:15:55 socket send error 32
2014-04-17 13:15:55 disconnecting node 178.203.9.140:62340
2014-04-17 13:16:11 Added 1 addresses from 62.75.167.102: 343 tried, 12760 new
2014-04-17 13:16:18 RegisterAsMasterNode
2014-04-17 13:16:19 Added 1 addresses from 213.229.88.102: 343 tried, 12761 new
2014-04-17 13:16:24 accepted connection 24.4.45.219:49030
2014-04-17 13:16:24 partner 24.4.45.219:49030 using obsolete version 60003; disc
onnecting
2014-04-17 13:16:24 ProcessMessage(version, 101 bytes) FAILED
2014-04-17 13:16:24 disconnecting node 24.4.45.219:49030
2014-04-17 13:16:26 Added 1 addresses from 171.93.181.107: 343 tried, 12762 new
2014-04-17 13:16:43 RegisterAsMasterNode
2014-04-17 13:16:48 accepted connection 66.178.182.35:34069
2014-04-17 13:16:48 send version message: version 70012, blocks=52910, us=54.213
.217.28:9999, them=66.178.182.35:34069, peer=66.178.182.35:34069
2014-04-17 13:16:48 Added time data, samples 18, offset -2 (+0 minutes)
2014-04-17 13:16:48 receive version message: /litecoinseeder:0.01/: version 7000
2, blocks=470000, us=54.213.217.28:9999, them=0.0.0.0:0, peer=66.178.182.35:3406
9
2014-04-17 13:16:49 Added 1 addresses from 213.229.88.102: 343 tried, 12761 new
2014-04-17 13:16:49 socket closed
2014-04-17 13:16:49 disconnecting node 66.178.182.35:34069
2014-04-17 13:16:52 accepted connection 176.31.186.58:33893
2014-04-17 13:16:53 send version message: version 70012, blocks=52910, us=54.213
.217.28:9999, them=176.31.186.58:33893, peer=176.31.186.58:33893
2014-04-17 13:16:53 Added time data, samples 19, offset +4 (+0 minutes)
2014-04-17 13:16:53 nTimeOffset = +5  (+0 minutes)
2014-04-17 13:16:53 receive version message: /litecoinseeder:0.01/: version 7000
2, blocks=470000, us=54.213.217.28:9999, them=0.0.0.0:0, peer=176.31.186.58:3389
3
2014-04-17 13:16:54 socket closed
2014-04-17 13:16:54 disconnecting node 176.31.186.58:33893
2014-04-17 13:17:00 Added 1 addresses from 173.48.74.21: 343 tried, 12761 new
2014-04-17 13:17:02 Added 1 addresses from 130.204.61.203: 343 tried, 12761 new
2014-04-17 13:17:06 Added 1 addresses from 80.203.63.210: 343 tried, 12761 new
2014-04-17 13:17:08 RegisterAsMasterNode

EDIT:
After removing peers.dat and waiting about an hour:

Code:
{
    "54.213.217.28:9999" : 1,
    "107.170.15.238:9999" : 1,
    "176.31.113.167:9999" : 1,
    "162.243.234.7:9999" : 1
}
 
Last edited by a moderator:
No update yet.
http://darkcoin.io/beta.php

What's your OS ?

Ubuntu on a amazon t1.micro (Linux ip-172-31-17-60 3.2.0-60-virtual #91-Ubuntu SMP Wed Feb 19 04:13:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux)

I have an automatic script that updates the daemon from the link you posted so I thought maybe some internal update or something...

Do you have you masternode list with the flag "1" ?

Did you see my edit on the post above? After removing peers.dat it connected to some nodes...
 
Ubuntu on a amazon t1.micro (Linux ip-172-31-17-60 3.2.0-60-virtual #91-Ubuntu SMP Wed Feb 19 04:13:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux)

I have an automatic script that updates the daemon from the link you posted so I thought maybe some internal update or something...

Do you have you masternode list with the flag "1" ?

Did you see my edit on the post above? After removing peers.dat it connected to some nodes...

some flag "0", some flag "1".

And I rejected those seeders.
https://darkcointalk.org/threads/wh...ldcoinseeder-try-to-check-darkcoin-nodes.263/
 
Question on Masternode list.

Does Masternode has cache time for Masternode list ?

When doing 'darkcoind masternode list', it still show 54.193.127.186.
54.193.127.186 is my old t1.micro's changed two days ago.


I think Masternode list is maintained by txid.
Cause "54.193.127.186" is not changed after node restart(also removing peers.dat).
 
I think Masternode list is maintained by txid.
Cause "54.193.127.186" is not changed after node restart(also removing peers.dat).

Well the root node Evan posted (23.23.186.131) is not available. Maybe we need to wait for a new update/information...
Meanwhile I cleared the .darkcoind folder except wallet, conf and peers.
 
Status
Not open for further replies.
Back
Top