NIS is using wrong boot key. Compare public keys of NIS
http://sn02.cyberblox.my:7890/node/info
and servant
http://sn02.cyberblox.my:7880/nr/metaData
Okay fixed it. There was a typo in the config file. Thank you very much!
Now waiting for several rounds to see if the changes are good.
Hey,
My two nodes have been failing more than usual on chain part and Height even some odd version failures for the last month. they have been working fine since the last update without many failures until now. Any ideas?
First thing to try usually is a restart of NIS. If it still fails tests after restart then maybe you should try a vps with more memory.
when I run the following command
<ps -ef |grep java>
I get this result
<user***** 2454 2452 3 12:30 ? 00:00:03 java -Xms128M -Xmx128M -cp .:servant/jars/* org.nem.rewards.servant.NodeRewardsServant
user***** 2521 2514 0 12:32 pts/0 00:00:00 grep java>
are all my java processes running like they should?
hi, is the supernode debian installation guide still up to date? Is Java 8 still required or older Java version required?
There should be two java processes running, the result looks like NIS is not up. Which supernode is it?
Not sure how “up to date” the guide is. Java version required is still Java 8.
Hey Bloodyrookie,
We are in the process of migrating nemster_2 to another VPS and have also sent a new enrollment message. When rebooting the server NIS does not start automatically. When I start it manually it shuts down after I log out. Do you have any suggestions?
Can you supply logs?
this?
nis-3.log
… 104 more
Caused by: org.apache.commons.codec.DecoderException: Illegal hexadecimal character at index 65
at org.apache.commons.codec.binary.Hex.toDigit(Hex.java:178)
at org.apache.commons.codec.binary.Hex.decodeHex(Hex.java:91)
at org.apache.commons.codec.binary.Hex.decode(Hex.java:232)
at org.nem.core.utils.HexEncoder.getBytesInternal(HexEncoder.java:43)
at org.nem.core.utils.HexEncoder.getBytes(HexEncoder.java:19)
… 105 more
(org.nem.deploy.CommonStarter a)
2019-09-23 13:59:19.665 INFO NEM Deploy 0.6.97-BETA shutdown… (org.nem.deploy.CommonStarter a)
So, looks like some key in the config is wrong. Please check all config entries.
it seems to work now according to the extended info. Still the node is failing all but the balance test. Was it enrolled with the new ip?
thanks again for your help
You don’t need to enroll again, you need to change the ip. So send a transaction with the message
change ip 46.252.27.237 to 45.76.38.124
to the noderewards account.
Hello, BloodyRookie.
I have a question.
Yesterday I tried to register the node.
My node is registered on this website (https://nemnodes.org/nodes/)
But my node is not registered on this website (https://supernodes.nem.io/).
Why is this?
The transaction hash is http://explorer.nemtool.com/#/s_tx?hash=2d44eb95ef285402cf74d2e358ae15857b0bb811af8d24cbc5a3fac9520a25e6.
The name is TEST01.
Your main account has only ~500 xem in it. To take part in the supernode program it needs to have at least 3M xem.
1 Like
Thank you!! @BloodyRookie . I did it!
And please change IP of these supernodes.
change ip 45.32.134.182 to 212.24.107.224
change ip 144.202.98.59 to 89.40.13.144
change ip 63.209.33.164 to 89.40.14.152
change ip 149.28.196.255 to 212.24.102.126
change ip 149.28.197.154 to 176.223.136.243
change ip 45.77.219.43 to 94.176.239.23
change ip 149.28.198.184 to 89.47.164.173
change ip 64.154.38.251 to 195.181.243.57
change ip 45.63.89.12 to 109.235.65.200
change ip 149.28.197.243 to 94.176.237.211
I already sent enroll message to NAFUND address,
the tx hash:
http://explorer.nemtool.com/#/s_tx?hash=aa2077aea6c4613760358a695561249eb0add1788cabde4c65c4f6da4f666276
http://explorer.nemtool.com/#/s_tx?hash=02b61e0b3880032af1219943e7bcc3eead4ec25c10e62fe6f45a0e0c3591f1f2
http://explorer.nemtool.com/#/s_tx?hash=05ede5710004e9290654f174f0d57772dc3e1cacc85f208ea24fd0c2a4e47016
http://explorer.nemtool.com/#/s_tx?hash=7157da82ccff7ad4c67cdadf5ae738fafd0c133e2066d331225dab0e19ab273d
http://explorer.nemtool.com/#/s_tx?hash=c88a44e435a1b56222ea5f5ead94ec7f43f3f3da9314125de36da3050b29bda4
http://explorer.nemtool.com/#/s_tx?hash=f6d14e71f99b3ec0b37fc32b777aaa30af1b60ca0ce5b57e0f305b7b963a8049
http://explorer.nemtool.com/#/s_tx?hash=cc7072f5b0e192e3eab61c7e917d57f0481fd4c668e075a2c18de8890bb5eedf
http://explorer.nemtool.com/#/s_tx?hash=8c67579caa8eefee07f1a73b2e61c635617530cab5a466e51e089e12784c2464
http://explorer.nemtool.com/#/s_tx?hash=493767cccfe969d443678f0e3fe7cd172cdd9d9c7829fd179463a677815e9e13
http://explorer.nemtool.com/#/s_tx?hash=77efe443f24155e9bfbdc627e51846490d2796cf9e619aaa6318437ee589d684
Thanks a lot!
How many time for getting the change ip effective ? since 2 days now and the ip at supernodes.nem.io is not updated. Thank you