NEM Supernode Rewards Program


#763

replacing the jar files should be enough.


#765

If you have installed it using this thread:

then you should ask in that thread.


#767

Thanks, all done and upgraded.


#768

Hello

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

Thanks


#769

IP change is already done.


#770

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


#771

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! :smiley:


#772

It worked.


#773

Cool, thanks :wink:


#774

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


#775

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


#776

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


#777

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.


#778

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


#779

I activated it.


#780

@BloodyRookie
Hey Chain-Master :wink:

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


#781

You are using a wrong boot key for your NIS. Public key in the database is

7f3b4088ca9bb24ed17ea75714da3c79bce4ff914193878a93569cbddda284fe

which is different from the key displayed in the extended info above.
Your servant has the correct key.


#782

Thanks for your hint!

My ~/nis-ncc/package/nis/config.properties had
#servant-key=xxxxxxx
after the update. (commented out). I corrected now with my private key and restarted. compared with the 0.6.79 version in that version’s file i had it -not- commented out and my key there.

That seemed to have been the issue. Now my extended-node-info shows the right pub-key.


#783

after I updated the nis version, I hit a similar issue which the node name was cheanged accidentally in my case. I had to remove the blockchain data and re-initialize again.

https://ponponpain.github.io/


#784

https://supernodes.nem.io/ seems to down now