[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[Lebubar]

Alright, I think we're good to go. All masternodes need to be running 10.16.11, everyone else can run anything past 16.6 and we'll be fine. Thanks to everyone who helped out!

10.16.11 Onyx V2 - All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.11-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.11-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.11-linux.tar.gz

I still get not capable masternode when I do darkcoind masternode debug on remote server instead of the other message that we used to get.... can't remember it but it directs you to look at the documentation. and I can't get the local to start a masternode because port 9999 is closed.  Could it be the port wasn't changed from testnet?

Double check the IP and both of your conf files...

[UdjinM6]

Alright, I think we're good to go. All masternodes need to be running 10.16.11, everyone else can run anything past 16.6 and we'll be fine. Thanks to everyone who helped out!

10.16.11 Onyx V2 - All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.11-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.11-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.11-linux.tar.gz

I still get not capable masternode when I do darkcoind masternode debug on remote server instead of the other message that we used to get.... can't remember it but it directs you to look at the documentation. and I can't get the local to start a masternode because port 9999 is closed.  Could it be the port wasn't changed from testnet?

you can check ports by

Code:

netstat -an | grep 9999

or

Code:

netstat -an | grep 19999

respectively

also check debug.log - maybe daemon banned your local machine for some time (24h by default)

Code:

cat ~/.darkcoin/debug.log | banned

you can remove peers.dat or/and try to use this option then

Code:

-bantime=<n>           Number of seconds to keep misbehaving peers from reconnecting (default: 86400)

[TanteStefana2]

I was excited there for a moment, because I hadn't checked my debug log.  Unfortunately, it shows nothing wrong.

Please understand, I can go back to 16.6 and get everything working fine, back and forth.  but anything higher and it fails as I've said (error with port on local and "not capable masternode" on remote server.

Unfortunately, 16.6 knocks off the network after a while  

Do you think I should change my ip addresses?  I don't want to because I have them memorized and that's kind of convenient....

[snogcel]

I was excited there for a moment, because I hadn't checked my debug log.  Unfortunately, it shows nothing wrong.

Please understand, I can go back to 16.6 and get everything working fine, back and forth.  but anything higher and it fails as I've said (error with port on local and "not capable masternode" on remote server.

Unfortunately, 16.6 knocks off the network after a while  

Do you think I should change my ip addresses?  I don't want to because I have them memorized and that's kind of convenient....

Did you issue a darkcoind masternode start on the local node?

[TanteStefana2]

I was excited there for a moment, because I hadn't checked my debug log.  Unfortunately, it shows nothing wrong.

Please understand, I can go back to 16.6 and get everything working fine, back and forth.  but anything higher and it fails as I've said (error with port on local and "not capable masternode" on remote server.

Unfortunately, 16.6 knocks off the network after a while  

Do you think I should change my ip addresses?  I don't want to because I have them memorized and that's kind of convenient....

Did you issue a darkcoind masternode start on the local node?

When I try that, with version > 16.6, I get a port error (port closed)  It's not closed. 

[snogcel]

I was excited there for a moment, because I hadn't checked my debug log.  Unfortunately, it shows nothing wrong.

Please understand, I can go back to 16.6 and get everything working fine, back and forth.  but anything higher and it fails as I've said (error with port on local and "not capable masternode" on remote server.

Unfortunately, 16.6 knocks off the network after a while  

Do you think I should change my ip addresses?  I don't want to because I have them memorized and that's kind of convenient....

Did you issue a darkcoind masternode start on the local node?

When I try that, with version > 16.6, I get a port error (port closed)  It's not closed. 

Would suggest running "tail -f debug.log" on your local node, then issuing that command again in another window (assuming this is linux). Might shed some light on where it's going wrong. Or maybe post your local darkcoin.conf here?

[Jesse Livermore]

****REFERENCE THIS POST 1 WEEK FROM TODAY****

 
Chart on top is a very small snippet from another asset's chart where I have seen this pattern DRK is in before. DRK chart for last 24 hours or so is on bottom. The referencing chart on top isn't to be used as a direct perfect picture of the future but is a general guideline.

And in general it's saying that we've got a little more rally left but are going to do a short-term top in the lower-.008 region in the next 24-48 hours and then proceed to consolidate, perhaps in a triangular pattern for 2-5 days before.....

All I'll say is I've just sent in a bunch of fiat and have locked in these soon-to-be-ridiculously low prices.
I might post the next small snippet next week. We'll see.
JL

Time to update the DRK chart and 'mystery asset' chart AND show more of the 'mystery asset's' chart...
Essentially, we are either now firmly in a large consolidation mode which will rally us back up a bit (but not to higher-highs above 0.0086) and we then go back to a double-low soon thereafter OR we go to higher-highs now and then some (0.012 target).
What is odd though is that DRK consistently has been "out-declining" the 'mystery asset' on the declines (like this recent decline just now technically was a sideways triangle on the 'mystery asset' chart but a nearly-full retracement for DRK) but DRK does keep up with the 'mystery asset's' price increases. I don't really have an explanation for that.
JL

[Minotaur26]

I was excited there for a moment, because I hadn't checked my debug log.  Unfortunately, it shows nothing wrong.

Please understand, I can go back to 16.6 and get everything working fine, back and forth.  but anything higher and it fails as I've said (error with port on local and "not capable masternode" on remote server.

Unfortunately, 16.6 knocks off the network after a while  

Do you think I should change my ip addresses?  I don't want to because I have them memorized and that's kind of convenient....

Did you issue a darkcoind masternode start on the local node?

When I try that, with version > 16.6, I get a port error (port closed)  It's not closed. 

Restart the instance, in the past that solved this for me.

[TanteStefana2]

Would suggest running "tail -f debug.log" on your local node, then issuing that command again in another window (assuming this is linux). Might shed some light on where it's going wrong. Or maybe post your local darkcoin.conf here?

Remote server:

Code:

ubuntu@ip-172-31-30-12:~$ tail -f .darkcoin/debug.log
2014-11-16 03:59:51 net thread interrupt
2014-11-16 03:59:51 Flushed 8642 addresses to peers.dat  40ms2014-11-16 03:59:51 Committing 296 changed transactions to coin database...
2014-11-16 03:59:51 Flush(true)
2014-11-16 03:59:51 wallet.dat refcount=0
2014-11-16 03:59:51 wallet.dat checkpoint
2014-11-16 03:59:51 wallet.dat detach

2014-11-16 03:59:51 wallet.dat closed
2014-11-16 03:59:51 DBFlush(true) ended              21ms
2014-11-16 03:59:51 Shutdown : done

Local:

Code:

ingiebee@HoneyPot:~/.darkcoin$ tail -f debug.log
2014-11-16 04:03:47 dseep: Signature rejected, too far into the past CTxIn(COutPoint(d09224a0b6b14d967279d32eab50761422622388b2e1217f18874197bd71c5ab, 0), scriptSig=)
2014-11-16 04:03:47 Misbehaving: 73.162.147.161:55581 (80 -> 100) DISCONNECTING
2014-11-16 04:03:47 disconnecting node 73.162.147.161:55581
2014-11-16 04:03:47 ProcessMessage(dseep, 116 bytes) FAILED
2014-11-16 04:03:48 socket closed
2014-11-16 04:03:48 disconnecting node 46.22.182.219:35435
2014-11-16 04:04:03 CDarkSendPool::UpdateState() == 3 | 3 
2014-11-16 04:04:25 Added 1 addresses from 54.93.207.88: 30 tried, 9705 new
2014-11-16 04:04:33 CDarkSendPool::UpdateState() == 3 | 3 
2014-11-16 04:05:03 CDarkSendPool::UpdateState() == 3 | 3 

And I've restarted my instances several times now

Thanks for trying to help!  Am I the only one with issues now?

Aha!  I did that quickly without reading, looks like my local has been banned!  do *I have to wait? or can I fix this?  Although those aren't my ip addresses???

[Lebubar]

Would suggest running "tail -f debug.log" on your local node, then issuing that command again in another window (assuming this is linux). Might shed some light on where it's going wrong. Or maybe post your local darkcoin.conf here?

Remote server:

Code:

ubuntu@ip-172-31-30-12:~$ tail -f .darkcoin/debug.log
2014-11-16 03:59:51 net thread interrupt
2014-11-16 03:59:51 Flushed 8642 addresses to peers.dat  40ms2014-11-16 03:59:51 Committing 296 changed transactions to coin database...
2014-11-16 03:59:51 Flush(true)
2014-11-16 03:59:51 wallet.dat refcount=0
2014-11-16 03:59:51 wallet.dat checkpoint
2014-11-16 03:59:51 wallet.dat detach

2014-11-16 03:59:51 wallet.dat closed
2014-11-16 03:59:51 DBFlush(true) ended              21ms
2014-11-16 03:59:51 Shutdown : done

Local:

Code:

ingiebee@HoneyPot:~/.darkcoin$ tail -f debug.log
2014-11-16 04:03:47 dseep: Signature rejected, too far into the past CTxIn(COutPoint(d09224a0b6b14d967279d32eab50761422622388b2e1217f18874197bd71c5ab, 0), scriptSig=)
2014-11-16 04:03:47 Misbehaving: 73.162.147.161:55581 (80 -> 100) DISCONNECTING
2014-11-16 04:03:47 disconnecting node 73.162.147.161:55581
2014-11-16 04:03:47 ProcessMessage(dseep, 116 bytes) FAILED
2014-11-16 04:03:48 socket closed
2014-11-16 04:03:48 disconnecting node 46.22.182.219:35435
2014-11-16 04:04:03 CDarkSendPool::UpdateState() == 3 | 3 
2014-11-16 04:04:25 Added 1 addresses from 54.93.207.88: 30 tried, 9705 new
2014-11-16 04:04:33 CDarkSendPool::UpdateState() == 3 | 3 
2014-11-16 04:05:03 CDarkSendPool::UpdateState() == 3 | 3 

And I've restarted my instances several times now

Thanks for trying to help!  Am I the only one with issues now?

Aha!  I did that quickly without reading, looks like my local has been banned!  do *I have to wait? or can I fix this?  Although those aren't my ip addresses???

There is too much time diference between your server?.?

2014-11-16 04:03:47 dseep: Signature rejected, too far into the past CTxIn(COutPoint(d09224a0b6b14d967279d32eab50761422622388b2

Did you try to delete peer.dat on both?

[TanteStefana2]

Would suggest running "tail -f debug.log" on your local node, then issuing that command again in another window (assuming this is linux). Might shed some light on where it's going wrong. Or maybe post your local darkcoin.conf here?

Remote server:

Code:

ubuntu@ip-172-31-30-12:~$ tail -f .darkcoin/debug.log
2014-11-16 03:59:51 net thread interrupt
2014-11-16 03:59:51 Flushed 8642 addresses to peers.dat  40ms2014-11-16 03:59:51 Committing 296 changed transactions to coin database...
2014-11-16 03:59:51 Flush(true)
2014-11-16 03:59:51 wallet.dat refcount=0
2014-11-16 03:59:51 wallet.dat checkpoint
2014-11-16 03:59:51 wallet.dat detach

2014-11-16 03:59:51 wallet.dat closed
2014-11-16 03:59:51 DBFlush(true) ended              21ms
2014-11-16 03:59:51 Shutdown : done

Local:

Code:

ingiebee@HoneyPot:~/.darkcoin$ tail -f debug.log
2014-11-16 04:03:47 dseep: Signature rejected, too far into the past CTxIn(COutPoint(d09224a0b6b14d967279d32eab50761422622388b2e1217f18874197bd71c5ab, 0), scriptSig=)
2014-11-16 04:03:47 Misbehaving: 73.162.147.161:55581 (80 -> 100) DISCONNECTING
2014-11-16 04:03:47 disconnecting node 73.162.147.161:55581
2014-11-16 04:03:47 ProcessMessage(dseep, 116 bytes) FAILED
2014-11-16 04:03:48 socket closed
2014-11-16 04:03:48 disconnecting node 46.22.182.219:35435
2014-11-16 04:04:03 CDarkSendPool::UpdateState() == 3 | 3 
2014-11-16 04:04:25 Added 1 addresses from 54.93.207.88: 30 tried, 9705 new
2014-11-16 04:04:33 CDarkSendPool::UpdateState() == 3 | 3 
2014-11-16 04:05:03 CDarkSendPool::UpdateState() == 3 | 3 

And I've restarted my instances several times now

Thanks for trying to help!  Am I the only one with issues now?

Aha!  I did that quickly without reading, looks like my local has been banned!  do *I have to wait? or can I fix this?  Although those aren't my ip addresses???

There is too much time diference between your server?.?

How would I fix that please?  Oh, and I forgot but 16.9 did work for me, but fell off the network...

[Lebubar]

Would suggest running "tail -f debug.log" on your local node, then issuing that command again in another window (assuming this is linux). Might shed some light on where it's going wrong. Or maybe post your local darkcoin.conf here?

Remote server:

Code:

ubuntu@ip-172-31-30-12:~$ tail -f .darkcoin/debug.log
2014-11-16 03:59:51 net thread interrupt
2014-11-16 03:59:51 Flushed 8642 addresses to peers.dat  40ms2014-11-16 03:59:51 Committing 296 changed transactions to coin database...
2014-11-16 03:59:51 Flush(true)
2014-11-16 03:59:51 wallet.dat refcount=0
2014-11-16 03:59:51 wallet.dat checkpoint
2014-11-16 03:59:51 wallet.dat detach

2014-11-16 03:59:51 wallet.dat closed
2014-11-16 03:59:51 DBFlush(true) ended              21ms
2014-11-16 03:59:51 Shutdown : done

Local:

Code:

ingiebee@HoneyPot:~/.darkcoin$ tail -f debug.log
2014-11-16 04:03:47 dseep: Signature rejected, too far into the past CTxIn(COutPoint(d09224a0b6b14d967279d32eab50761422622388b2e1217f18874197bd71c5ab, 0), scriptSig=)
2014-11-16 04:03:47 Misbehaving: 73.162.147.161:55581 (80 -> 100) DISCONNECTING
2014-11-16 04:03:47 disconnecting node 73.162.147.161:55581
2014-11-16 04:03:47 ProcessMessage(dseep, 116 bytes) FAILED
2014-11-16 04:03:48 socket closed
2014-11-16 04:03:48 disconnecting node 46.22.182.219:35435
2014-11-16 04:04:03 CDarkSendPool::UpdateState() == 3 | 3 
2014-11-16 04:04:25 Added 1 addresses from 54.93.207.88: 30 tried, 9705 new
2014-11-16 04:04:33 CDarkSendPool::UpdateState() == 3 | 3 
2014-11-16 04:05:03 CDarkSendPool::UpdateState() == 3 | 3 

And I've restarted my instances several times now

Thanks for trying to help!  Am I the only one with issues now?

Aha!  I did that quickly without reading, looks like my local has been banned!  do *I have to wait? or can I fix this?  Although those aren't my ip addresses???

There is too much time diference between your server?.?

How would I fix that please?  Oh, and I forgot but 16.9 did work for me, but fell off the network...

Well do
date
On both wallet to check.. (can try date -u to have universal time)

Then change it : and put the same on both
sudo date --set "15 Nov 2014 22:17:00"

Or can sincronized with a server :
sudo ntpdate ntp.online.net

[TanteStefana2]

Yup, one shows Sunday's date and the other shows Saturday's date (it's still Saturday here) UTC and PST, though I would think, since they know what time zone they're in, it shouldn't matter?

[Lebubar]

Yup, one shows Sunday's date and the other shows Saturday's date (it's still Saturday here)

Make date -u (in case you are on diferent time zone on your server)

Yes maybe this ... look :
2014-11-16 04:03:47 dseep: Signature rejected, too far into the past CTxIn(COutPoint(d09224a0b6b14d967279d32eab50761422622388b2

[tungfa]

Please Tip UdjinM6
for his great job !!
Tx
XsV4GHVKGTjQFvwB7c6mYsGV3Mxf7iser6
 

[TanteStefana2]

Yup, one shows Sunday's date and the other shows Saturday's date (it's still Saturday here)

Make date -u (in case you are on diferent time zone on your server)

Yes maybe this ... look :
2014-11-16 04:03:47 dseep: Signature rejected, too far into the past CTxIn(COutPoint(d09224a0b6b14d967279d32eab50761422622388b2

I remember installing ntp on my remotes, I don't think it's on my local.  I'm slow, and working on this.  I will update if this helps, sorry for the time span!!!  But thanks so far, it's my best bet!

[Lebubar]

Yup, one shows Sunday's date and the other shows Saturday's date (it's still Saturday here)

Make date -u (in case you are on diferent time zone on your server)

Yes maybe this ... look :
2014-11-16 04:03:47 dseep: Signature rejected, too far into the past CTxIn(COutPoint(d09224a0b6b14d967279d32eab50761422622388b2

I remember installing ntp on my remotes, I don't think it's on my local.  I'm slow, and working on this.  I will update if this helps, sorry for the time span!!!  But thanks so far, it's my best bet!

Yes sure it's the remote. I see 4 min less on your remote and the message say : too far into the past
Just put 4 min more on your remote.

Or as root on both : ntpdate ntp.online.net

[HinnomTX]

Please Tip UdjinM6
for his great job !!
Tx
XsV4GHVKGTjQFvwB7c6mYsGV3Mxf7iser6
 

Tips sent! I woke up on version 6 and ended up loading version 11. Amazing work today! Now off to bed.

[DiCE1904]

If someone writes a detailed guide on how to have more than one masternode within a wallet ill send ya 100DRK for your service.

[TanteStefana2]

Well, I found how to sync my date/time, and did so on both machines, but I still get "not capable masternode".  I am able to start my masternode on the local, however, but it's not showing up on my remote when I do masternode debug

I don't think I'm banned anywhere because my debug lists a different ip address (doesn't belong to my internal or external ip) unless the ip address listed is for the one banning me?

But at least my local hot wallet was able to start.... maybe that's progress ??