Cool)) remind me please that files needs to be replaced to update node
The jars whose names begin with "nem".
when is last dayfor updated our supernodes at last version ?
Probably 2016-11-06, so roughly 2 weeks from now.
Is it possible to show the servertime on the supernodes Website (maybe in the footer something like: loaded at 11:00 a clock" or so) I can't figure out when my server was scanned and if it was while my upgrading. ... hmm(Just a thought)
Not sure i understand. The time when the supernode was tested (scanned as you put it), is shown in the website.For example the node Alice2 was tested for bandwidth in round 1245 at Mon Oct 24 2016 10:39:44 GMT+0000:
Or did you mean something else?
Hi,maybe it helps a look at your servant (Linux console). You can see the ping-pongs and the inquiry. After that you know, it´s time to update.
I have moved my supernode to a different server.
Node name is "LeChuck".
The old IP was 188.8.131.52
The new IP is 184.108.40.206
Is this sufficient or do I need to send a message on the network?
Please take a look at the first post of this thread. You need to send a message to the node rewards account again.The message should be like:change ip 220.127.116.11 to 18.104.22.168
replacing the jar files should be enough.
If you have installed it using this thread:
then you should ask in that thread.
Thanks, all done and upgraded.
My supernode 'SloNode1' has new IP 22.214.171.124. The old IP was 126.96.36.199
IP change is already done.
Update your supernode(s) to version 0.6.82Failing to do so will result in failed version testThe reference NIS will be updated on sunday 2016-11-13
Hello BloodyRookie, I had to change bcn's supernode IP.
I just sent the 'change ip 188.8.131.52 to 184.108.40.206' message.
Hey BloodyRookie, could you please tell me why it's failing all the tests? The logs show alright and didn't change anything but the ip.
http://220.127.116.11:7880/nr/metaDatadoes not respond.
NIS seems to have a wrong boot key, i can see"INFO couldn't verify response from node 'bcn '"Public key i see when doing a /node/info request on your node is6facdaf82261adf27b81738c1e2464ab016a165ca9070fcfa37313ba55fed563
public key in the db is658cb53d8762abe659163c0eb08c329c3677c651a68e883a01e771749a67f476