Update to 0.9.4.4 or 0.10.8.4 to prepare for the hardfork on May 25!

Evan's comment on Bitcointalk forum sounded like payments were already starting, but that can't be can it?
 
chaeplin said:
I have removed flasg ' 0 ' entry, now 22.


user@sv2:~> darkcoind masternode list | grep ' 1' | sort -n | uniq | wc -l
22
user@sv2:~> darkcoind masternode count
58
Click to expand...


E


My nodes are returning 57 active in the list

Code: 
./darkcoind masternode list | grep ':\ 1' | sort -n | uniq
    "107.170.137.60:9999" : 1,
    "107.170.139.43:9999" : 1,
    "107.170.143.175:9999" : 1,
    "107.170.156.6:9999" : 1,
    "141.255.184.191:9999" : 1,
    "142.161.23.40:9999" : 1,
    "172.245.215.22:9999" : 1,
    "184.73.179.148:9999" : 1,
    "184.73.179.187:9999" : 1,
    "184.73.179.196:9999" : 1,
    "188.226.133.22:9999" : 1,
    "188.226.225.170:9999" : 1,
    "188.226.230.170:9999" : 1,
    "188.226.232.243:9999" : 1,
    "188.226.248.36:9999" : 1,
    "192.99.184.44:9999" : 1,
    "192.99.184.45:9999" : 1,
    "192.99.184.46:9999" : 1,
    "192.99.184.48:9999" : 1,
    "192.99.184.49:9999" : 1,
    "192.99.184.50:9999" : 1,
    "192.99.184.51:9999" : 1,
    "192.99.184.52:9999" : 1,
    "192.99.184.54:9999" : 1,
    "192.99.184.55:9999" : 1,
    "192.99.184.57:9999" : 1,
    "192.99.184.58:9999" : 1,
    "192.99.184.60:9999" : 1,
    "192.99.184.62:9999" : 1,
    "54.178.168.241:9999" : 1,
    "54.186.116.211:9999" : 1,
    "54.186.36.157:9999" : 1,
    "54.187.112.94:9999" : 1,
    "54.187.147.18:9999" : 1,
    "54.187.152.9:9999" : 1
    "54.187.61.169:9999" : 1,
    "54.255.148.0:9999" : 1,
    "54.255.149.109:9999" : 1,
    "54.72.17.216:9999" : 1,
    "54.72.209.87:9999" : 1,
    "54.72.58.75:9999" : 1,
    "54.76.19.70:9999" : 1,
    "54.76.7.191:9999" : 1,
    "54.76.7.195:9999" : 1,
    "54.76.7.196:9999" : 1,
    "54.76.7.198:9999" : 1,
    "54.76.7.201:9999" : 1,
    "54.76.7.202:9999" : 1,
    "54.76.7.203:9999" : 1,
    "54.76.7.204:9999" : 1,
    "54.84.135.47:9999" : 1,
    "54.86.103.191:9999" : 1,
    "80.38.144.39:9999" : 1,
    "81.71.76.162:9999" : 1,
    "91.121.219.246:9999" : 1,
    "94.132.162.92:9999" : 1,
    "94.23.22.195:9999" : 1,
    "98.101.247.254:9999" : 1,


EDIT: 60

Code: 
$ ./darkcoind masternode list | grep ':\ 1' | sort -n | uniq | wc -l

60
 
Last edited by a moderator:
With this new version I see both my masternodes actives (from remote/local configuration with cold storage). Let's see how it looks in a few hours. :) But I am already feeling better. :D
 
think that would be a better way of getting the correct count

darkcoind masternode list | grep ' : 1' | sort -n | uniq | wc -l

your will match ips that have a 1 in them as well
 
flare said:
You can escape the whitespace with a backslash \ in front

Code: 
darkcoind masternode list | grep ':\ 1' | sort -n | uniq | wc -l
Click to expand...
On my systen, don't need escape \
' 1' == '\ 1'


Placing \ is good practice though.

Code: 
user@sv2:~> darkcoind masternode list | grep ':\ 1' | sort -n | uniq | wc -l
37
user@sv2:~> darkcoind masternode list | grep ': 1' | sort -n | uniq | wc -l
37
user@sv2:~> darkcoind masternode list | grep ' 1' | sort -n | uniq | wc -l
37
 
chaeplin said:
http://drk.poolhash.org/masternode.html

wait 10 -20 min.

Let's check again.
Click to expand...

Current node count on my node(s): 67

Code: 
$ ./darkcoind masternode list | grep ':\ 1' | sort -n | uniq | wc -l
67

Perhaps you should consider deleting peers.dat and restarting your daemon


UdjinM6 said:
33 only ^^^
and on my masternodes I'm getting 68
ps. I added few nodes manually (addnode=xxx.xxx.xxx.xxx) in conf file on every my masternode - that could do the trick for you too I guess
Click to expand...

Thats exactly what i did, too
 
Last edited by a moderator:
 
My masternode is not showing up, even in it's own masternode list yet it said masternode started successfully. Any ideas of what happened?

edit: w00t updated to 10.8.6 and it's found.
 
Last edited by a moderator:
eduffield said:
Version 9.4.6 and 10.8.6

Another improvement to help the network sync. After most of us update, we should start to see network consensus.

Source code:
https://github.com/darkcoinproject/darkcoin

Stable version (v0.9.4.6):
http://www.darkcoin.io/downloads/darkcoind
http://www.darkcoin.io/downloads/darkcoin-qt
http://www.darkcoin.io/downloads/darkcoin-qt.exe

RC2 (v0.10.8.6):
http://www.darkcoin.io/downloads/rc/darkcoind
http://www.darkcoin.io/downloads/rc/darkcoin-qt
http://www.darkcoin.io/downloads/rc/darkcoin-qt.exe
Click to expand...
Do we have to do the masternode genkey procedure after each update? And do the local and the remote darkcoind both need their own key?
My MN is still not showing up. I guess I'll wait til more people have updated and will try again tomorrow
 
eduffield

user@sv2:~> darkcoind masternode count
78
user@sv2:~> darkcoind masternode list | grep '9999' | grep '\ 1' | sort -n | uniq | wc -l
32


uw2Xsnc.png

7yCHVPu.png


Sudden drop of no of NM.
Is Masternode sync period related to block generation time ?
 
UdjinM6 said:
33 only ^^^
and on my masternodes I'm getting 68
ps. I added few nodes manually (addnode=xxx.xxx.xxx.xxx) in conf file on every my masternode - that could do the trick for you too I guess
Click to expand...
UdjinM6 said:
10.8.6 works much better for me (no need to add nodes manually)
Click to expand...

Updated to 10.8.6, network sync seems more stable.

Nevertheless the nodes still drop out of the network sync from time to time, e.g. 78 active nodes in list, drop to 5 active nodes in 10 minutes time. After restart with deletion of peers.dat back to 78 active nodes again.

I am currently monitoring the no. of active nodes on all my nodes and do a restart each time a node show a anomaly. I hope that this gets sorted out till payment launch.
 
flare said:
Updated to 10.8.6, network sync seems more stable.

Nevertheless the nodes still drop out of the network sync from time to time, e.g. 78 active nodes in list, drop to 5 active nodes in 10 minutes time. After restart with deletion of peers.dat back to 78 active nodes again.

I am currently monitoring the no. of active nodes on all my nodes and do a restart each time a node show a anomaly. I hope that this gets sorted out till payment launch.
Click to expand...
having issues too - after some time my nodes are listed with 0 but they are alive.... something is not good... :sad:

EDIT: removing peers.dat helps: 41 "active" node -> 87
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top