OK, will check tomorrow morning and activate them again if they got the necesssary balance.
Hello @BloodyRookie
I had to change the remote key for my supernode.
I sent a new enrollment transaction:
Hash: da6a40d55757d0c618f797ed2f4ab9496dde289567808f2bbfe1ba7aafdc4088
Multisig hash: d0836b03843236029cce48641825c9ecda524bc9e4bbc94a04edcc9b42521793
Can you, please, activate it and deactivate the old rigel11 supernode?
Thank you
Deactivated the old one and added the new one.
1 Like
Hi @BloodyRookie .
please change IP of these supernodes.
Change ip 23.236.76.102 to 167.88.178.55
Change ip 23.236.76.15 to 167.88.178.56
I already sent enroll message to NAFUND address,
the tx hash:
Thank you.
IPs were changed.
Hi @BloodyRookie .
Sorry, the new system error has been resolved, please apply for IP recovery. The application is as follows:
please change IP of these supernodes.
Change ip 23.236.76.102 to 167.88.178.55
Change ip 23.236.76.15 to 167.88.178.56
I already sent enroll message to NAFUND address,
the tx hash:
http://explorer.nemtool.com/#/s_tx?hash=e8ed564836b1a7a920c32b4cdbfdfef7e2423b1eb40a5dbccf9fda43963ae880
This one has wrong formatting, you forgot the āChange ipā part. Try again.
Hi @BloodyRookie
Application has been resend, please confirmļ¼
http://explorer.nemtool.com/#/s_tx?hash=7be291e296b4eb2d3f4e73967d14035c3b293f4b1add7704ce0be9b1131661da
Ip was changed.
The ip address for the supernode KingsLandingUsesNEM2 has changed:
change ip 216.189.147.206 to 45.58.52.38
Below is the hash transaction. Thanks.
https://explorer.nemtool.com/#/s_tx?hash=e5a51a3977df467cd65deefc27da92038fd59d710ac183e8331b2da7fadbe3a9
Change was successful.
I noticed the test results and the according payouts for the last 10 days have been extremely unstable in the NIS1 SN system, even much more unstable than we are used to.
I know there must be some work and developments going on for the Symbol SN system. Are these efforts influencing the stability of the NIS1 SN system? Or is there any other reason or clarification for this instability?
As always, it is almost impossible to investigate the performance of our nodes, as the failed tests do not provide any info about the reason of failure, besides āno test resultā, while the nodes are up and running and seem to be running ok from my point of view.
I had a lot of instability too, it went away when I increased Xmx to 7G.
That might have been coincidence.
My nodes have Xmx 7G and 8G while instability appears on both, so donāt think memory is causing issues, as also tests succeeded afterwards without reboot or restart.
So there must be other sources of these instability issues.
My best guess is that the connections from the master to the supernodes were instable. Maybe somewhere between the US and the rest of the world there was a problem. But I think it is getting better again or do the problems persist?
It has been two days more stable, but now unreliable again as 1/3 of nodes have failed tests.
I donāt understand, because I perform my own tests of a few API calls each day, sometimes multiple times per day. And those tests always succeeded the last weeks, also today.
While in the SN system there are again some tests with āNo results to showā.
helloļ¼@BloodyRookie
Apply to reactivate āpvknem001ā nodeļ¼
enroll 167.88.178.56 pvknem001 9e960becadacb0588f1a1ac82eff5368c66d6834e2f4e3b6fb9c68e6904359f9
I already sent enroll message to NAFUND address,
the tx hash:
bf8a4aa70fb986e56121a9a7bd3939067a5cb7f101abc93a7e8c859187f14f24
Thanks!
Done.
Hello @BloodyRookie
Our team applied to activate mycointainer_com Node
Here is our message:
enroll 163.172.31.181 mycointainer_com 43c3b1503d694f3562d1ffd7ca088663e0d9eaaf7ab6c4012716301b1c75395f
TxHash: 66bca4ca9d2176058403f947030a7e82bc58dbea5cfcb712f2f40e9e6429cc98
Weāre still not visible in https://supernodes.nem.io (we enrolled 3 days ago)
Will you be able to tell me what should I change or help me in any other way?
Thanks in advance!