NEM Supernode Rewards Program

Blog Posts
#1117

I am using a local ip for now.

I had to turn off delegate harvesting for now because in trying to figure things out, I removed my account from the wallet, create a new account to start delegate harvesting, then added account back in, then delegate harvest seems to have been corrupt, giving me an error message when I try to start delegate harvesting.

#1118

And that works or not?

#1119

No it does not. Says NIS not available

#1120

Then your local NIS is not running ^^

#1121

But NCC that is on the same folder as NIS is running fine…ie. the default setting

#1122

Maybe I can come back after delegate harvesting is enabled so you can see and test on my NIS?

#1123

Try

http://127.0.0.1:7890/chain/height

if that doesn’t work, your NIS is not running.

#1124

The page returns “height 1093700”. This is from NIS host.

This is the rest of NCC config setting:
nem.httpPort = 8989
nem.httpsPort = 9090
nem.webContext = /ncc/web
nem.apiContext = /ncc/api
nem.homePath = /index.html
nem.shutdownPath = /shutdown

#1125

Then the ncc setting are wrong, can you paste an image of the ncc setting popup (tab Remote Server)?

Edit:

Those are the config.properties, i am talking about the settings in the browser page.

1 Like
#1127

After changing the setting it works now. Thank you so much. Now, do I need to change the configuration file back to default or it doesn’t matter?

#1128

If it works you don’t need to change it…

1 Like
#1129

Hi,
I sent enroll message for supernode croissant 88.99.87.132

Transfer transaction
From
NBBTED-R3LHFA-XJQOM5-3BFH3V-QWDMB2-H5JMKX-DKFH
To
NAFUND-BUKIOS-TMD4BN-XL7ZFE-735QHN-7A3FBS-6CMY
Amount
30.000000 XEM
Fee
4.000000 XEM
Message
enroll 88.99.87.132 croissant 9836a4447eb608657d49c94bff2d3458d2989706a843ddaae98dec8a3a4e94a3
Block
1096490
Hash
8686a9c10417ceb6af535d0324821b2e75b0275e1bf088a370fe39289f35bba5

the above is re-enrollment for machine
node 88.99.87.132 croissant deactivated february 2
enrolled with NCC delegated public key 5e1f9d35b7bead2f1f96a8f1ba07df229fdc50b8382a0ad4d6bcf9f8c91f1ec7

#1130

@quasarblue: reenrollment with a different public key but same name / ip is not automated. I need to add the new entry manually.

Edit: done: https://supernodes.nem.io/details/639

#1131

Great!

#1132

Hello BloodyRookie I sent you a message with IP change. Regards,

#1133

Seems the message was not processed, maybe because you attached the " thank you" at the end. Changing the ip is automated and the bot doesn’t like additional stuff that it can’t interprete. Let me check with QM to see if that was the reason it failed.

#1134

The reference NIS was upgraded to version 0.6.87. All supernodes running a prior version will fail the version test from now on.

2 Likes
#1135

Hi! I am having some problems since I upgraded the nis. I can see this on the servant’s log:

2017-05-07 22:09:59.804 WARNING ping completed with exception: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException (org.nem.rewards.servant.servlets.PingTaskServlet lambda$performSingleRound$9)

https://supernodes.nem.io/history/search/bcn

Do you have any idea on what may be causing this? I tried rebooting but nothing

Thanks!

#1136

@bcn: your node is doing fine again.

#1137

Thanks BR!