NEM Supernode Rewards Program

[BloodyRookie]

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:

http://supernodes.nem.io/archive/1/1245

Or did you mean something else?

[garm]

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.

[blue]

I have moved my supernode to a different server.

Node name is “LeChuck”.

The old IP was 176.28.11.34

The new IP is 192.241.220.107

Is this sufficient or do I need to send a message on the network?

Thanks

[BloodyRookie]

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 176.28.11.34 to 192.241.220.107

[BloodyRookie]

Do we delete the package folder and replace with the contents of the package folder from the updated 0.6.82 tgz file, or is it as simple as replacing the jar files in the console, nis, ncc and monitor folders?

replacing the jar files should be enough.

[BloodyRookie]

If you have installed it using this thread:

NEM Supernode Command Line Tutorial for Debian 8.4

This tutorial will show you how to set up a supernode for NEM on a VPS with Debian 8.4 via the command line in three steps. Also take a look at: http://blog.nem.io/supernodes/ http://blog.nem.io/supernodes-start/. ###Command Line Knowledge### We are going to use vim as our text editor. You can also use nano if you are more familiar with it. For a basic vim tutorial visit: English: https://www.linux.com/learn/vim-101-beginners-guide-vim German: https://wiki.ubuntuusers.de/VIM/ http…

then you should ask in that thread.

[suky321]

Thanks, all done and upgraded.

[Xember]

Hello

My supernode ‘SloNode1’ has new IP 54.246.167.90. The old IP was 54.171.4.194

Thanks

[BloodyRookie]

My supernode ‘SloNode1’ has new IP 54.246.167.90. The old IP was 54.171.4.194

IP change is already done.

[BloodyRookie]

Update your supernode(s) to version 0.6.82
Failing to do so will result in failed version test
The reference NIS will be updated on sunday 2016-11-13

[bcn]

Hello BloodyRookie, I had to change bcn’s supernode IP.

I just sent the ‘change ip 185.14.185.109 to 146.185.167.160’ message.

Thanks!

[BloodyRookie]

I just sent the ‘change ip 185.14.185.109 to 146.185.167.160’ message.

It worked.

[bcn]

Cool, thanks

[bcn]

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://supernodes.nem.io/details/327

Thanks

[BloodyRookie]

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://146.185.167.160:7880/nr/metaData
does 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 is
6facdaf82261adf27b81738c1e2464ab016a165ca9070fcfa37313ba55fed563

public key in the db is
658cb53d8762abe659163c0eb08c329c3677c651a68e883a01e771749a67f476

[BloodyRookie]

The following nodes have been failing every day for a long time. If the owners of those supernodes don’t fix the problems, the supernodes will get deactivated next weekend:

• Budapest: NIS / servant problems
• KamilX2: insufficient balance
• Jerry2: NIS / servant problems + insufficient balance
• MyGaga3: NIS / servant problems + insufficient balance
• MyGaga1: NIS / servant problems + insufficient balance
• Alpha3: NIS / servant problems + insufficient balance
• NEM-Supernode-Qingdao: insufficient balance
• Alpha2: insufficient balance
• Alpha1: NIS / servant problems + insufficient balance
• Jerry1: NIS / servant problems + insufficient balance
• Noise: NIS / servant problems + insufficient balance
• nemxembos: NIS / servant problems + insufficient balance
• EU2.rohan: NIS problems
• Gorenger: NIS problems
• himmelsfaller3: NIS / servant problems
• mnbhsgw: NIS / servant problems
• Tray: NIS / servant problems + insufficient balance
• taro: NIS problems
• supernova: NIS / servant problems
• UK01SuperNode: NIS / servant problems
• Penter3: NIS problems
• Shibuya001: NIS / servant problems

If you need help with your supernode, please post in this thread

[meyns]

Penter3 has passed the last 2 rounds now, so everything is working now.
Thanks for pointing it out btw, I didn’t know the node was failing the tests.

[lcharles123]

Can you activate my node, please? nem.servehttp.com
Thanks!

[BloodyRookie]

Can you activate my node, please? nem.servehttp.com
Thanks!

I activated it.

[r3n3]

@BloodyRookie
Hey Chain-Master

Can you advise what could be wrong in Africa?

http://197.242.90.170:7890/node/extended-info

{"node":{"metaData":{"features":1,"application":null,"networkId":104,"version":"0.6.82-BETA","platform":"Oracle Corporation (1.8.0_101) on Linux"},"endpoint":{"protocol":"http","port":7890,"host":"197.242.90.170"},"identity":{"name":"NBX572RVRZDBOQVIFALKXUTGXY2YJNLLT3SZNFUU","public-key":"9f5fd95c82b5a15d6f977a8e5623112c88e0c971b019845d6169657207469705"}},"nisInfo":{"currentTime":51177424,"application":"NEM Deploy","startTime":51089279,"version":"0.6.82-BETA","signer":null}}

http://supernodes.nem.io/details/392:

Info: That happened since I upgraded to 0.6.82 few days ago.
Info2: Am running Ubuntu 16.04 and not Debian.

Peace,
R3n3