v0.10.16 - Onyx v2

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
Fixed it with this: "shutdown all, delete peers.dat on local and remote, startup all, send masternode start twice a few seconds apart"
All credit goes to moocowmoo!
thanks again mate ;)
Tried this and it didn't help, MN disappeared from the list after less than 60 mins.
 

GermanRed+

Active Member
Aug 28, 2014
299
109
113
Maybe there should be 2 week period when only bugs get fixed.
Jira issues is growing pretty fast.
I don't mind immediate fix. But, upgrading all MN's immediately sounds like a bad idea. We had reports of these issues so it would be better if we were not asked to choose between upgrade or get no MN payment.
 

strix

Well-known Member
Foundation Member
Sep 14, 2014
140
121
193
The Shadow Lands
this issue with darksend fees was most important, and its not like those 34 bugs are very important - wallet works great most of the time. and evan already made it clear that he needs more developers. so lets just be happy he gets so much work done and not tell him what to do next
+1
No doubt Evan has a sense of both what he thinks is most important, and what would require the most time. It might be useful to him if MN owners took a vote listing their three most important concerns. Not as a gripe or demand on Even, but simply to give him and the other developers more data for their prioritizing.
 

Lebubar

Active Member
Mar 15, 2014
249
213
103
Hi,

So I see that I'm not alone.
To confirm what said by Yikadee
I just made the downgrade of 1 of my MN to 15.21 : only start the deamon remote (I don't make masternode start from local)
And after few seconds I saw all my 6 MN from this MN (15.21)...
The downgrade MN : saw 1186 masternode in his list (with 1)
All the other (16.6) saw 237 or 236 MN in the list..

I will not stat my MN every hour, so just wait for the coding machine =)
 

ourlink

Well-known Member
Foundation Member
Jun 9, 2014
237
65
188
Heartland, USA
www.p2poolmining.us
Just my opinion... So take it for what it is worth. (I have been in the software development field for over 30 years).

Important "Production" bug fixes need to be corrected and deployed as quickly as possible to get your production system back up and running as expected. But that bug fix should only include the fix that addresses the production issue. Other small bug fixes should be rolled out through the normal release cycle only after adequate unit testing, system testing, and regression testing have been performed.

All of the recent releases have really caused a disconnect between the pools, miners and masternodes... For instance, look at the list of P2Pool (p2pools.org/drk)pools and you will quickly see that amongst the 135 or so pools running darkcoin, there are probably 6 - 8 different versions of the darkcoin daemon being run! (you can see this by sorting and reviewing the different values in the global hashrate column).

I'm ranting because, while I like all of the quick updates and bleeding edge technology... We need to fix the immediate production issue and allow all pools, miners, and MN's to get back in sync, let the dust settle, then get back to a normal release cycle!

Stop the craziness....
 

jiggytom

Member
Nov 14, 2014
104
22
68
Mine have been on since last night and grep still returns my IP. I'm on 16.6. I did have to shut everything down twice before it did show up though (cold and then hot wallet)
 

Lebubar

Active Member
Mar 15, 2014
249
213
103
I can almost certainly confirm its a cosmetic issue. definitely one of my "dropped" 16.6 nodes got payed. It does not show up through the VPS daemon list, shows as :0 through v.16.6 local VM machine, and shows as :1 listed from any v.15.21 daemon.
Maybe.. Mine did not recieved a payment yet..
I made your test with only one downgrade and yes exctly the same..
We will see, and I will check if the 5 still on 16.6 receive a payment today...
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
My mistake though, Got payed to a downgraded v.15.21. But fernando just confirmed my suspicions on BTCtalk. So yeah,seems like something is going on with 16.6 that is not "MN dropping"
 

booyah

New Member
Apr 18, 2014
15
2
3
same here MN keeps dropping/disappearing and i keep having to restart MN`s, hope patch comes out soon as there is a problem.
 

Lebubar

Active Member
Mar 15, 2014
249
213
103
My mistake though, Got payed to a downgraded v.15.21. But fernando just confirmed my suspicions on BTCtalk. So yeah,seems like something is going on with 16.6 that is not "MN dropping"
Yes, but are you sure that his masternode was not listed at one moment, then was on the list to be paid, then disapeared, then get paid...
As I know you can be paid some time after your MN got unlisted. (don't know exactly how is done the list "to be paid"(or valid) but I imagine that at each round a valid list is made and keep valid for the all the round...)
I didn't restart my MN since now 10h and will not, and for the moment no payment.

We'll need to wait for a patch I think, but I hope that Evan's gf(wife not sure) let him work on week end! :rolleyes:
-"What ? Another bug to hunt? When we will have a week end together?"
lol :D
 

Lebubar

Active Member
Mar 15, 2014
249
213
103
From BCT :
eduffield said:
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/.../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/DR...-win-darkcoin-dist/darkcoin-0.10.16.7-win.zip
 

maky

Member
Nov 14, 2014
71
32
58
Version 10.16.7:
341 wget
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

sorry, I can not add link (after wget). Find it on net. Someone must like my post once... :)
 

Ch0nG

Member
Oct 3, 2014
50
34
58
Has anyone got Darksend to work?

I understand the network needs to be updated but I've tried for the last two nights to use Darksend with no luck. The client (under Linux) keeps looping with:
"Darksend is idle" => "Submitted to masternode, waiting in queue" => "Darksend is idle"

Occasionally it says:
"Darksend is idle" => "Submitted to masternode, waiting in queue" => "Darksend request incomplete: Last darksend was too recent. Will retry..." => "Darksend is idle"
 

GilAlexander

Member
Jun 26, 2014
84
23
48
Updated mn to 10.16.7, got <myip>:0 in the list after half an hour. Updated cold wallet, restarted mn. Deleted peers.dat on both sides.
 

Lebubar

Active Member
Mar 15, 2014
249
213
103
Updated mn to 10.16.7, got <myip>:0 in the list after half an hour. Updated cold wallet, restarted mn. Deleted peers.dat on both sides.
Same here my MN updated in 16.7 got ": 0" in the list after less than one hour...
EDIT: And after get unlisted...
 
Last edited by a moderator:

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
Me too, after 60 mins goes to :0 then vanishes. I noticed on drk.mn the 'active duration' remained at 1s the whole time, as if it pings the network when launched, then sits there not talking anymore?