v0.10.16 - Onyx v2

[Lebubar]

6.5 MN updated without problem all seen all of them.
Great work again!

But they don't see the same number of MN :
lebubar@104:~$ ./darkcoind masternode list | grep ": 1" | wc -l
204
____
lebubar@install:~$ ./darkcoind masternode list | grep ": 1" | wc -l
163
__________
lebubar@108:~$ ./darkcoind masternode list | grep ": 1" | wc -l
173

we have to wait to stabilized =)

 

[snogcel]

updated with no problems!

question -- with removed darksend fees, does that mean there is now no cost of running a liquidity provider?

 

[tungfa]

Question:
There was somewhere a comment/post that this update has
Start Multiple for MN's build in ?!
Can anybody please provide a guide/explanation how this works
Tx

 

[strix]

I noticed Even mentioned something about "Darksend request incomplete. Last darksend was too recent". That it would not happen often, but it could still come up under some circumstances and when you first start up.

I am trying to "Mix" and I am getting this "Darksend request incomplete. Last darksend was too recent". Anyone else seeing this continuously? (I have not used my wallet for about a week before opening it today.)

I am getting the same thing, but I had my wallet opened last night before updating today. How long should I wait before trying again?

 

[UdjinM6]

Sorry to annoy you but there is still something wrong

masternode list lastseen
...........
........
"104.156.231.81:9999" : 1416014572,
"176.31.190.77:9999" : 1416013860,
"188.226.180.119:9999" : 2045615525,
"188.226.228.88:9999" : 2045775280,
"80.240.135.83:9999" : 2045945974,
"95.85.1.197:9999" : 2046103671,
"107.170.157.166:9999" : 2046184866,
"95.85.48.49:9999" : 2046343833,
"188.226.196.182:9999" : 2046506665,
"188.226.201.140:9999" : 2046666796,
"107.170.242.110:9999" : 2046790382,
........
......

And that just can't be true: 1416014572 for example is Sat, 15 Nov 2014 01:22:52 GMT but 2045615525 is Sat, 28 Oct 2034 02:32:05 GMT
( http://www.onlineconversion.com/unix_time.htm )
and there are a lot of them...
I wouldn't be worry too much about it but I guess that could prevent "DarkSend Election Entry Ping" (dseep) message from propagating and that's actually the message that should tell everyone else that your MN is alive as far as I understand (normally you should send it every 20 minutes)
https://github.com/darkcoin/darkcoin/blob/master/src/masternode.cpp#L178-L181
The source of such behavior is there I believe
https://github.com/darkcoin/darkcoin/blob/master/src/activemasternode.cpp#L227
It should say

masterNodeSignatureTime = GetAdjustedTime();

and not

masterNodeSignatureTime = GetTimeMicros();

eduffield flare

 

[JGCMiner]

I am getting the same thing, but I had my wallet opened last night before updating today. How long should I wait before trying again?

Having the same "last Darksend too recent" problem as well. No successful denominations thus far on 16.6...

 

[djcrypto]

All my MNs are updated and showing up on client debug window 'masternode list' command.
No rewards yet though. Will give it a day or two.
Cheers!

 

[moli]

Enforcement is off?

 

[moli]

From Evan...
"Masternode payments for version 16.6+ have begun! This means, there will be no more payments for the old network until they update.

Enjoy the extra payments

"

https://bitcointalk.org/index.php?topic=421615.msg9548125#msg9548125

 

[Lebubar]

Well after maybe 2 hours all my MN were unlisted...
Restared them from local. Will monitor later again.
They list more or less 200 Mn, with small diference from one to other.

Edit: and again after some times all unlisted again...
All now have 205 :
lebubar@MN6:~$ ./darkcoind masternode list | grep ": 1" | wc -l
205

Am I alone with this problem, all my MN get unlisted after some times?

In the trace I can only see for the moment message like this :
2014-11-15 02:18:25 Removing inactive masternode 108.61.219.39:9999

 

[djcrypto]

Same all mine got unlisted. Just restarted them. Will see how long they last...FYI I did get a paid once in that time period so I think they're "working". Just maybe a problem with stability?

 

[AjM]

Same all mine got unlisted. Just restarted them. Will see how long they last...FYI I did get a paid once in that time period so I think they're "working". Just maybe a problem with stability?

Same here, ALL my MN:s drops off from the list.
Its my new dayjob, starting all day long my MN:s.:sad:

 

[AjM]

Am I alone with this problem, all my MN get unlisted after some times?

Any info how fast they drop off the list?

 

[AjM]

Any info how fast they drop off the list?

Watching this how long MN:s are listed and when they drop off the list, reporting back when they get unlisted.
Last start: 10:49...

 

[jpr]

same here they dissapear after like 2 hours
When I do

masternode start password

in local wallet they come back

 

[Raico]

Same here, ALL my MN:s drops off from the list.
Its my new dayjob, starting all day long my MN:s.:sad:

Same Here~ log send~
Hope may help~

Edit: drop list about one hour.

 

[AjM]

Watching this how long MN:s are listed and when they drop off the list, reporting back when they get unlisted.
Last start: 10:49...

OK, MN:s dropped about after one hour, not good if need restart every hour.

 

[GilAlexander]

Dropped off after an hour too, just now.

Suddenly I got two payments on onyx2: 13 hours ago and now.

 

[GermanRed+]

Enforcement is off?

View attachment 624

It wasn't off last night some time after I started the upgraded daemon. However, after my MN's got kicked off like what happened to others, the enforcement is off since I restarted them.

 

[AjM]

OK, MN:s dropped about after one hour, not good if need restart every hour.

JIRA issue done http://jira.darkcoin.qa/browse/DRK-120