Ghost Masternode Piniging?

[camosoul]

I have a node who's VM has been shut down and destroyed. The network still shows it active and pinging several hours later.

I'd like to start up the new node in the new location, but it won't drop off the network... I'm curious how something that physically doesn't even exist anymore can still be pinging and active...

 

[splawik21]

I've noticed that behaviour in the past as well. To take it off the network I had to refund the address with 1000 coins.

 

[crowning]

I have a node who's VM has been shut down and destroyed. The network still shows it active and pinging several hours later.

I'd like to start up the new node in the new location, but it won't drop off the network... I'm curious how something that physically doesn't even exist anymore can still be pinging and active...

Unfortunately I have zero time right now to investigate WHY this happens, but when you do a "masternode genkey" with the wallet which holds the 1000 DASH vin, stop the wallet, change the key in both the wallets and the Masternodes config files, start the wallet and the Masternodes dashd and start the new Masternode with "masternode start" from within the wallet the old one will (normally) immediately drop off the Masternode list.

 

[camosoul]

Oh, I understand how to force the matter. I was just hoping to do it the sane way... Since I can't SSH to the nodes (they're on pure IPv6, and my home ISP actually forbids use of IPv6, I can't even do an HE tunnel because they actively block traffic). I have to use the virtual ESXi console, which can't copy/paste... Re-typing all that shit is a major pain in the ass, and just begs for typos... It could take weeks assuming I don't make any mistakes... I've got a whole rack of these things to do...

This node just got a payment and it has physically been unplugged from the network and power for many hours now... That's a pretty serious bug. Masternodes that don't exist, and clearly are not Providing Service, get paid... Proof of Service? Wut?

I didn't realize it was a known issue. No worries then... Sort of...