- Apr 15, 2014
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.Maybe there should be 2 week period when only bugs get fixed.
Jira issues is growing pretty fast.
+1this 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
The suggested patch does not completely fix the issue. The MN's will still become non-active (i.e. grep will return : 0).
Maybe.. Mine did not recieved a payment yet..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.
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...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"
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):
Same here my MN updated in 16.7 got ": 0" in the list after less than one hour...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.