systemnode won't start after update to v0.12.5.2

[skironDotNet]

updated hot wallet QT and VPS binary, and systemnode privatekey, and it just won't start keep saying:

"status" : "Not capable systemnode: Hot node, waiting for remote activation."

[TheExiledMonk]

did you update the privkey in both the systemnode.conf file on your desktop, and in the crown.conf in your VPS?

…

On Fri, Nov 23, 2018 at 7:50 PM Pawel Cioch ***@***.***> wrote: updated hot wallet QT and VPS binary, and systemnode privatekey, and it just won't start keep saying: "status" : "Not capable systemnode: Hot node, waiting for remote activation." — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#95>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB0r39D3C9zk_RTKb-YVMhGU5wpNKi0rks5uyEOFgaJpZM4YxCJF> .

-- Mvh Fabian Olesen

---- If it moves, compile it.

[skironDotNet]

At first I didn't hoping SN is going to pick up being active (the grace period) then I started SN with old key and nothing then I realized since its a new protocol I may bed to do that, so I did and nothing.

Have 12 connections on Linux SN, the QT on win synced, and it doesn't start. I'm not at home right now. But after a few hours all cashed activations should expire so I'm going to try again, but never had a problem like this before after any upgrade. Never had to even replace the key.

The Crown devs didn't mention if old protocol still makes rewards and at what block it will expire like they did on prev protocol updates

[TheExiledMonk]

it should not be needed to change the privkey as far as i know, and it should pick up node just fine, but try when you get back home to start it again, else ping me on discord - same name

[skironDotNet]

Works, I think everybody needs to wait 2h for the activation cache to expire, it work without changing the key.

And here is my comment from discord
re: "I don't think you need to change the pivate key, I think after you stop MN you need to wait 30-90min for the MN activation cache to expire" In theory changing the key should make it expired right away but maybe nodes keep MN cache by MN IP and so changeing the key doesn't help. Just stop your node wait 2h and start it then

[TheExiledMonk]

yeah, i think it was because not many had changed over to the new one yet, glad its solved :)