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

[GilAlexander]

Evan, you want the debug.log? (even if I don't see anything "special")

Is there a way to increase trace level?

Naw, the debug I need would be on your peers.
I'm compiling a new version, we'll see if that works.

OK, perfect, I'm ready for next upgrade.

Alright, try this and let me know:

http://www.darkcoin.io/binaries/darkcoin-0.10.16.8-linux.tar.gz

Deleted peers.dat, updated.

[Lebubar]

Evan, you want the debug.log? (even if I don't see anything "special")

Is there a way to increase trace level?

Naw, the debug I need would be on your peers.
I'm compiling a new version, we'll see if that works.

OK, perfect, I'm ready for next upgrade.

Alright, try this and let me know:

http://www.darkcoin.io/binaries/darkcoin-0.10.16.8-linux.tar.gz

Deleted peers.dat, updated.

Did it but with local wallet on 16.7 because on windows and binary not yet ready.
Did you make it with 16.8 local wallet (if it's linux)?
Or maybe not important the version of local wallet (as the protocol version of MN should be the same)

[Cryptosis]

Funny how trolls were complaining about paying the tax to the masternodes and spamming every thread try could to Fud people into scamming the system to avoid payments. So since the couldn't Fud dark into oblivion they decide to join the community and set up masternodes and collect the tax from miners of the coin they claimed to despise and tried to destroy. In all honesty it hasn't been very long and some dark members have been overly forgiving to said trolls, oh how easily one forgets the atrocities of another. I just don't get it, how anyone could welcome said people after the things that were said and done to harm the community.

[GilAlexander]

Deleted peers.dat, updated.

Did it but with local wallet on 16.7 because on windows and binary not yet ready.
Did you make it with 16.8 local wallet (if it's linux)?
Or maybe not important the version of local wallet

Updated hot wallet only, have ":1" in list now. Will wait.

[innergy]

3 MN updated without deleting peers.dat, started from 16.7 Win.. seems OK for now.

[innergy]

Deleted peers.dat, updated.

Did it but with local wallet on 16.7 because on windows and binary not yet ready.
Did you make it with 16.8 local wallet (if it's linux)?
Or maybe not important the version of local wallet

Updated hot wallet only, have ":1" in list now. Will wait.

Ok
2 MN updated.
lebubar@install:~$ ./grepMN.sh
MN1
MN2
MN3
MN4
MN5
    "108.x.x.x:9999" : 1,
MN6
    "128.x.x.x:9999" : 1

Will keep posted in ~1 hour

How is going your "last seen" on https://drk.mn/?

[Lebubar]

Deleted peers.dat, updated.

Did it but with local wallet on 16.7 because on windows and binary not yet ready.
Did you make it with 16.8 local wallet (if it's linux)?
Or maybe not important the version of local wallet

Updated hot wallet only, have ":1" in list now. Will wait.

Ok
2 MN updated.
lebubar@install:~$ ./grepMN.sh
MN1
MN2
MN3
MN4
MN5
    "108.x.x.x:9999" : 1,
MN6
    "128.x.x.x:9999" : 1

Will keep posted in ~1 hour

How is going your "last seen" on https://drk.mn/?

I don't check drk.mn.
Because he didn't update since : drkmn02   Running   101606

But yes I'm listed for the moment :
128:9999   Open (33m20s)   0.10.16.6   XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX[1][2]   1,000.000   3w2d16h27m17s   43m30s   United States   Active (100%)
Hmmmm but it didn't have my real good version =)

lebubar@MN6:~$ ./darkcoind getinfo
{
    "version" : 101608,

Also he say that his site updated only once every hour...

[GilAlexander]

Deleted peers.dat, updated.

Did it but with local wallet on 16.7 because on windows and binary not yet ready.
Did you make it with 16.8 local wallet (if it's linux)?
Or maybe not important the version of local wallet

Updated hot wallet only, have ":1" in list now. Will wait.

Ok
2 MN updated.
lebubar@install:~$ ./grepMN.sh
MN1
MN2
MN3
MN4
MN5
    "108.x.x.x:9999" : 1,
MN6
    "128.x.x.x:9999" : 1

Will keep posted in ~1 hour

How is going your "last seen" on https://drk.mn/?

3m for me.

[thelonecrouton]

Also just started up a fresh MN with 16.8, fingers crossed.

[innergy]

3 MN updated without deleting peers.dat, started from 16.7 Win.. seems OK for now.

Over 50min. "last seen".. not very optimistic. Maybe we should rollback to 15.21 and start fighting this fee issue from the scratch..

[fuze0000]

Keep up the hardwork at the darkcoin community!

[jiggytom]

3 MN updated without deleting peers.dat, started from 16.7 Win.. seems OK for now.

Over 50min. "last seen".. not very optimistic. Maybe we should rollback to 15.21 and start fighting this fee issue from the scratch..

Thousands of lines of code have been changed...Evan will figure it out.

//updated to v8, will see what happens.  It was odd that I was fine on v6, not good on v7 though.  v6 I used a new IP...so maybe that goes back to what someone mentioned about the IPs having to drop off the old clients?

[Lebubar]

3 MN updated without deleting peers.dat, started from 16.7 Win.. seems OK for now.

Over 50min. "last seen".. not very optimistic. Maybe we should rollback to 15.21 and start fighting this fee issue from the scratch..

Thousands of lines of code have been changed...Evan will figure it out.

//updated to v8, will see what happens.  It was odd that I was fine on v6, not good on v7 though.  v6 I used a new IP...so maybe that goes back to what someone mentioned about the IPs having to drop off the old clients?

Did you leave your local wallet online? when you were on v16.6?

[HinnomTX]

Maybe the masternode must be removed from the old V15 list for it to propagate correctly on the V16 list? All my MNs have been booted from the V16 list but they are still on the V15 list even though they've been running the new software for a day or so.

Bump. I have 3 MNs still running the old V15 software. When I tried 'darkcoind masternode stop' on the remote server I got 'Successfully stopped masternode'. My IP briefly registered "xxx.xxx.xxx.xxx:9999" : 0 but within minutes was back to :1 and has stayed there. Behavior was the same for all 3 MNs. I still think there's a potential conflict in having a MN appear on both V15 and V16 lists simultaneously. It's harder to test this theory when you can't get yourself booted from the older MN list (and maybe that's the heart of the problem). Time to test with fresh IPs.

[jiggytom]

3 MN updated without deleting peers.dat, started from 16.7 Win.. seems OK for now.

Over 50min. "last seen".. not very optimistic. Maybe we should rollback to 15.21 and start fighting this fee issue from the scratch..

Thousands of lines of code have been changed...Evan will figure it out.

//updated to v8, will see what happens.  It was odd that I was fine on v6, not good on v7 though.  v6 I used a new IP...so maybe that goes back to what someone mentioned about the IPs having to drop off the old clients?

Did you leave your local wallet online? when you were on v16.6?

yes..always leave my local wallet on. 

[Lebubar]

3 MN updated without deleting peers.dat, started from 16.7 Win.. seems OK for now.

Over 50min. "last seen".. not very optimistic. Maybe we should rollback to 15.21 and start fighting this fee issue from the scratch..

Thousands of lines of code have been changed...Evan will figure it out.

//updated to v8, will see what happens.  It was odd that I was fine on v6, not good on v7 though.  v6 I used a new IP...so maybe that goes back to what someone mentioned about the IPs having to drop off the old clients?

Did you leave your local wallet online? when you were on v16.6?

yes..always leave my local wallet on.  

Hmmmm this confirm, my feeling...

Because your the only one I saw saying it was ok on 16.6.
Now I've made a test with 16.8.
the one with local wallet offline go unlisted after 1 hour. (MN5)
The other with local wallet online, still listed after 1 hour(MN6). (and also have MN5 listed)...

Maybe something with new protocol don't like to be cut from his mumy (local wallet) ?

Also someone else on dct say that his only MN still listed (after one night) was the one with his local wallet online..

[thelonecrouton]

16.8 showing more signs of life, at least on drk.mn - active duration 33m and last seen 2m ago. Local wallet offline. Will see what happens in another 30 mins.

[innergy]

My masternodes are still listed on drk.mn (16.8 already) and "last seen" is updating often - 2min., 8min., 4min...
But they are ... :0 on the remote ./darkcoind masternode list..

EDIT: And .. :1 again without restarting.. maybe 16.8 is OK 

[eduffield]

16.8 showing more signs of life, at least on drk.mn - active duration 33m and last seen 2m ago. Local wallet offline. Will see what happens in another 30 mins.

Yeah, I think v16.8 will fix 90%+ of the clients that can't keep active. Masternodes should also set maxconnections=100+ in their configuration, if v16.8 is the fix that will have an impact as well.

[eduffield]

Oooo My MN5 came back from the grave and listed again (without doing anything).

lebubar@[MN5]:~$ date ; ./grepMN.sh
Sat Nov 15 21:00:44 UTC 2014
MN1
MN2
MN3
MN4
MN5
    "108.x.x.x:9999" : 1,
MN6
    "128.x.x.x:9999" : 1,


will keep monitoring this...

That's exciting. I think we're in business. I'll roll out the official version