Done.
sent the message
Deactivated.
@BloodyRookie I sent an enroll tx a day ago to update my supernode alias and new pubkey (due to transfer XEM to Trezor) but it seems to be not updated yet, I have updated the boot key in both NIS and servant config file. Anything else that I missed? Status of the node seems ok.
Added it manually and deactivated old one.
1 Like
@BloodyRookie I’ve sent 2 change IP msgs
From Himmelsfalller 2
change ip 95.130.254.153 to 85.10.248.125
From himmelsfaller 3
change ip 95.130.254.155 to 85.10.248.126
The IP’s should be active in 1 hour
I got 2 new IP’s over a third party and I hope they’ve changed Himmelsfaller 2 to 85.10.248.125
and himmelsfaller 3 to 85.10.248.126 and not vice versa. Otherwise I will send another change IP
msg. We will see as soon the servers are booted with the new IP’s.
ok the nodes are now loading the chain. (at 1,4 mio blocks at the moment). it may take one more hour to be fully loaded. there was a delay with changing the nodes.
@BloodyRookie
ok the provider acidentally exchanged the ip’s .
in supernodes.nem.io is Himmelsfaller 2 with 85.10.248.125
and himmelsfaller3 with 85.10.248.126 but in
http://85.10.248.125:7890/node/extended-info is himmellsfaller3
and in http://85.10.248.126:7890/node/extended-info is Himmelsfaller 2
I just sent now a change ip request from the wallets.
From Himmelsfaller 2
change ip 85.10.248.125 to 85.10.248.126
From himmelsfaller3
change ip 85.10.248.126 to 85.10.248.125
thank you for changing that.
Changed it.
@BloodyRookie
Hi BR himmelsfaller3 has the wrong ip
it should have 85.10.248.125 but in supernodes.nem.io it shows
85.10.248.126. That’s the same ip as Himmelsfaller 2 has.
Himmelsfaller 2 passes, but himmelsfaller3 always fails.
Is it because of the wrong ip in the supernodes.nem.io list.
The node should work as listed in 85.10.248.125:7890/node/extended-info and chain is actualized. as seeable in 85.10.248.125:7890/chain/height
Thanks for helping.
I had changed it to 85.10.248.125, probably the bot changed it back cause you some change message you send. Anyway, i changed it back to …125, let’s see if it works this time.
@BloodyRookie
Thanks for changing. But it seems that the bot now changed Himmelsfaller 2 to
85.10.248.125 too. Or could it be a problem with the private delegated key, because one of the keys (have to check if it was Himmelsfaller 2 or himmelsfaller3) was from the old NEM NCC wallet. Maybe that confuses the bot?
Currently i am not sure why some nodes have problems passing this test. All my nodes, no matter where they reside on this planet, are passing the test with few exceptions.
Which nodes are you talking about?
Hi,
supernode http://88.99.87.132 “croissant”
is going on maintenance.
There are currently 20 harvesters
each one of them needs to independently reactivate later.
When the network migrates to Catapult, what will happen to the supernodes? Is the program going to continue in any way?
Thanks
Migration and Supernodes related questions are not yet decided.
@BloodyRookie registered a new supenode
https://supernodes.nem.io/details/1090
No test results are showing up - is this normal?
maltablock
IP: 107.150.46.98