MN got unlisted even in 16.7 and removing peer.dat... After ~1 hour..
Strange. Look at the time on your hot node and see if it's correct, maybe the network is rejecting the pings because of that.
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 3499. (Read 9723748 times)
November 15, 2014, 01:14:33 PM
Strange. Look at the time on your hot node and see if it's correct, maybe the network is rejecting the pings because of that.
November 15, 2014, 01:09:37 PM
MN got unlisted even in 16.7 and removing peer.dat... After ~1 hour..
November 15, 2014, 01:08:10 PM
probably/hopefully a fake upmove
driven by 500 drk.. just too less coins on the book, next move upward will happen quickly
November 15, 2014, 01:07:45 PM
Masternodes still kicking offline on v7 even with remote and local peers.dat deleted.
November 15, 2014, 01:03:17 PM
probably/hopefully a fake upmove
November 15, 2014, 12:43:17 PM
MNs out after an hour after deleting peers.dat local and remote
getpeerinfo gave me new peers only
will check 10.16.7 now
Ok so you did this with 16.6.getpeerinfo gave me new peers only
will check 10.16.7 now
For 16.7 Still listed ok after 45 min =)
I get paid while I was online btw
I had that happen on v7 on a few masternodes. I solved it by stopping the remote daemons, deleting peers.dat, deleting peers.dat on local and trying again. Eventually it just said masternode started and grepped the ip with a 1 in the masternode list.
November 15, 2014, 12:36:35 PM
MNs out after an hour after deleting peers.dat local and remote
getpeerinfo gave me new peers only
will check 10.16.7 now
Ok so you did this with 16.6.getpeerinfo gave me new peers only
will check 10.16.7 now
For 16.7 Still listed ok after 45 min =)
I get paid while I was online btw
November 15, 2014, 12:30:28 PM
MNs out after an hour after deleting peers.dat local and remote
getpeerinfo gave me new peers only
will check 10.16.7 now
Ok so you did this with 16.6.getpeerinfo gave me new peers only
will check 10.16.7 now
For 16.7 Still listed ok after 45 min =)
November 15, 2014, 12:27:43 PM
MNs out after an hour after deleting peers.dat local and remote
getpeerinfo gave me new peers only
will check 10.6.7 now
getpeerinfo gave me new peers only
will check 10.6.7 now
November 15, 2014, 12:21:01 PM
16.7 looks much better.
Now I have more than 340 listed on masternode list.
With 16.6 never go more than 250...
edit: still need one hour or two to confirm if all OK.
Now I have more than 340 listed on masternode list.
With 16.6 never go more than 250...
edit: still need one hour or two to confirm if all OK.
November 15, 2014, 12:10:00 PM
strange flat pricemove on cryptsy ...
This is the same type of calmness we saw before the last run up!
BTC on the downtrend too..which means its cheaper to get DRK. It's only a matter of time before we are back in the .008s.
November 15, 2014, 12:07:35 PM
strange flat pricemove on cryptsy ...
This is the same type of calmness we saw before the last run up!
he likes to deke
November 15, 2014, 12:02:24 PM
strange flat pricemove on cryptsy ...
This is the same type of calmness we saw before the last run up!
November 15, 2014, 12:00:40 PM
just updated on mine. My IP shows in list (didn't have issues in 16.6) . Masternode count shows 272 on both hot and cold wallet. So far so good!
Masternode Update
There's a few possible reasons that some of you are getting delisted.
1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)
To figure out which one you are:
1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.
You can also also try 10.16.7 (this version will ONLY connect to new peers):
Linux 64:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind
Windows:
http://bamboo.darkcoin.qa/browse/DRKW-DEV-36/artifact/JOB1/gitian-win-darkcoin-dist/darkcoin-0.10.16.7-win.zip
There's a few possible reasons that some of you are getting delisted.
1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)
To figure out which one you are:
1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.
You can also also try 10.16.7 (this version will ONLY connect to new peers):
Linux 64:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind
Windows:
http://bamboo.darkcoin.qa/browse/DRKW-DEV-36/artifact/JOB1/gitian-win-darkcoin-dist/darkcoin-0.10.16.7-win.zip
November 15, 2014, 11:59:53 AM
Total Masternodes: 1184 = 1184 actives + 0 inactives
Estimated daily payout: 0.46 DRK/day
0.10.16.6: 52.2%
0.10.15.21: 33.9%
https://drk.mn/masternodes-v15.html
I don't know what's up with https://drk.mn/
-onetime
Estimated daily payout: 0.46 DRK/day
0.10.16.6: 52.2%
0.10.15.21: 33.9%
https://drk.mn/masternodes-v15.html
I don't know what's up with https://drk.mn/
-onetime
November 15, 2014, 11:54:29 AM
It is work , thx Evan 
November 15, 2014, 11:53:29 AM
amazing coin & dev!
November 15, 2014, 11:50:43 AM
BTW, i have lot's of charts showing potential masternode earnings that i made to show investors i know. Shall i post them?
Yes please. November 15, 2014, 11:41:34 AM
Masternode Update
There's a few possible reasons that some of you are getting delisted.
1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)
To figure out which one you are:
1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.
You can also also try 10.16.7 (this version will ONLY connect to new peers):
Linux 64:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind
Windows:
http://bamboo.darkcoin.qa/browse/DRKW-DEV-36/artifact/JOB1/gitian-win-darkcoin-dist/darkcoin-0.10.16.7-win.zip
There's a few possible reasons that some of you are getting delisted.
1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)
To figure out which one you are:
1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.
You can also also try 10.16.7 (this version will ONLY connect to new peers):
Linux 64:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind
Windows:
http://bamboo.darkcoin.qa/browse/DRKW-DEV-36/artifact/JOB1/gitian-win-darkcoin-dist/darkcoin-0.10.16.7-win.zip
OK
Already upgrade one :
341 wget http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind
344 ./darkcoind stop
345 cd .darkcoin/
346 ls -ltr
347 rm peers.dat
348 cd ..
349 ls -ltr
350 rm darkcoind
351 mv darkcoind.1 darkcoind
352 chmod u+x darkcoind
353 ./darkcoind
Start it localy, listed ok on all my MN, will monitor if it still listed after one hour or two.
If ok, will upgrade all.
EDIT : well I'll upgrade another (forgot to delete peer.dat on local =))
So fisrt upgrade with only delete peer.dat on remote.
Second upgrade : delete peer.dat on both local and remote.
Both listed : OK
Will monitor after one hour. and keep informed.
November 15, 2014, 11:39:04 AM
Masternode Update
There's a few possible reasons that some of you are getting delisted.
1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)
To figure out which one you are:
1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.
You can also also try 10.16.7 (this version will ONLY connect to new peers):
Linux 64:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind
Windows:
http://bamboo.darkcoin.qa/browse/DRKW-DEV-36/artifact/JOB1/gitian-win-darkcoin-dist/darkcoin-0.10.16.7-win.zip
There's a few possible reasons that some of you are getting delisted.
1. You're not connected to enough peers on the new network (I've confirmed this to be the case on 2 of 3 of the nodes I've looked at)
2. The ping messages in the previous version weren't working correctly and nodes weren't delisted when they should have been. Your setup might not be correct, in this case it would have worked last time.
3. You used start-many, which had a bug in the ping timestamp (fixed in 10.16.17)
To figure out which one you are:
1.) Delete peers.dat (both remote and local)
2.) Start the masternode remotely, afterward you can type "masternode start" on the hot node and it should say "remotely started masternode". If it says "not capable", then you'll need to debug what the problem is.
You can also also try 10.16.7 (this version will ONLY connect to new peers):
Linux 64:
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-38/gitian-linux-darkcoin-bin/bin/64/darkcoind
Windows:
http://bamboo.darkcoin.qa/browse/DRKW-DEV-36/artifact/JOB1/gitian-win-darkcoin-dist/darkcoin-0.10.16.7-win.zip
Deleted peers dat local and remote, installed 16.7 local and remote, started MN from local qt, fine, ran masternode start on remote, got 'masternode started remotely' - so far so good...
Jump to: