Shouldn’t be a problem as long as the first account still has at least 3M xem.
i have on the balance 6M and 5.95 vested balance can i send 3M to the second account for one more super node?
NA4OHK-QT3XAA-VE62NR-WD6EJF-5FVQGS-M7T5E4-CWQF
3kk+
errors in nis.log
2018-01-23 05:06:57.125 WARNING Timer BROADCAST raised exception: org.nem.core.connect.FatalPeerException: Peer returned 500 with error: <?
2018-01-23 05:20:48.790 INFO Updating “Node [Skynode03 ] @ [160.16.235.155]” -> ACTIVE (org.nem.peer.services.NodeRefresher update)
2018-01-23 05:20:48.790 SEVERE INDIRECT fatal error encountered while communicating with <Node [NAA5A3YLMLCUUBN7H4KJWOSF542M5HTARM2IIRE5 ] @ [13.112.0.77]>: java.util.concurrent.CompletionException: org.nem.peer.node.ImpersonatingPeerException: entity source cannot be verified (org.nem.peer.services.NodeRefresher a)
2018-01-23 05:22:29.073 INFO Http Status Code 404: Not Found (org.nem.core.connect.ErrorResponse )
Is it normal?
I already answered that question:
Looks like either NIS and Servant are not running or the ports 7890 and 7880 are not open.
http://195.2.88.7:7890/node/info
http://195.2.88.7:7880/nr/metaData
does not return any response.
@M_M: those errors indicate that some of the other nodes in the network are not working properly, that has nothing to do with your node. As long as your node passes all tests, everything is fine.
ah… sorry did not understand at first time thank you.
http://195.2.88.7:7890/node/info1
http://195.2.88.7:7880/nr/metaData
now works.
My Servant does not do ping-pong:
2018-01-23 05:50:46.988 INFO NEM logging has been bootstrapped! (org.nem.deploy.LoggingBootstrapper bootstrap)
2018-01-23 05:50:46.996 INFO Starting embedded Jetty Server. (org.nem.rewards.servant.NodeRewardsServant main)
2018-01-23 00:50:47.060:INFO::main: Logging initialized @758ms
2018-01-23 00:50:47.159:INFO:oejs.Server:main: jetty-9.2.11.v20150529
2018-01-23 00:50:47.209:INFO:oejsh.ContextHandler:main: Started o.e.j.s.ServletContextHandler@5c5a1b69{/nr,null,AVAILABLE}
2018-01-23 00:50:47.246:INFO:oejs.ServerConnector:main: Started ServerConnector@4bbfb90a{HTTP/1.1}{0.0.0.0:7880}
2018-01-23 00:50:47.246:INFO:oejs.Server:main: Started @943ms
2018-01-23 05:50:47.246 INFO Node rewards org.nem.rewards.servant is ready to serve. (org.nem.rewards.servant.NodeRewardsServant startServer)
Is it a problem in Servant?
Doesn’t work for me. Are NIS and Servant running?
ok, now i see the problem. You send the enroll message two times, the first time with IP address 195.2.88.7. Since the IP address was valid, the bot made the entry in the database. The second enroll message was ignored since there already was a database entry using the same public key.
You can change the ip in the database by sending a message to the noderewards account:
change ip 195.2.88.7 to 195.2.88.77
from the account you used for enrolling.
Thank you
fail 
Please give it 24 hours.
Change the ip on my supernode, I sent several messages, according to the instructions, the change in force did not come.
Tokyo1 45.32.250.78 to 104.156.249.108
Sorry
Tokyo1 45.32.250.78 to 104.156.249.109
I changed it manually.
I just creat supernode two days ago, IP=47.91.76.32,node name=hellonem, but it’s not accept yet, I have send message to the official node rewards account.