NEM Supernode Rewards Program

All i see in the master log is that the node is not responding to the /chain/height requests that are used for the responsiveness test. The log looks like this:

2018-05-12 22:27:59.856 INFO Responsiveness for node Yggdrasil: 10/10 (525ms) (org.nem.rewards.master.task.ResponsivenessTask lambda$null$49)
2018-05-12 22:27:59.873 INFO Responsiveness for node nemster: 0/10 (541ms) (org.nem.rewards.master.task.ResponsivenessTask lambda$null$49)
2018-05-12 22:27:59.906 INFO Responsiveness for node Neonoda: 10/10 (574ms) (org.nem.rewards.master.task.ResponsivenessTask lambda$null$49)

Maybe the NIS log of your node can help. Could you provide the log for that time?

Hi @BloodyRookie
Fyi, at round 3499, a lot of nodes failed the balance test.
https://supernodes.nem.io/history/1252586

I am aware of that. Those nodes will receive manual payout.

Here are the payouts for the nodes that failed the balance test due to NIS restart on the node rewards server:
payouts.pdf (37.2 KB)

BloodyRookie hi, could you please change ip from 172.106.32.50 → 185.122.58.143 for xem1xem1xem?

Thanks in advance

Done.

please activate:
cybertribe.tuxflow.de” nem message to nafbu… was sendet allready…

Can you give me the tx hash?

http://chain.nem.ninja/#/transfer/4ea68c1058834f6f146ea7dca4d489de0aa1464307d1b1fd35ae9b99d5c82f66

@PleaseActivate: will check a bit later.

Edit: here you go:
https://supernodes.nem.io/details/976

1 Like
  • did i have to send a msg to “nalice” too ? the nis.bootkey ist the “delegated private key” from the adress with the xem on it, the adress that was used to send the enroll msg… delegated harvesting is set (deactivated and activated it yesterday), but reported balance is still zero…

There is something misconfigured with the domain cybertribe.tuxflow.de.
The request
cybertribe.tuxflow.de:7890/node/info
redirects to
https://cybertribe.tuxflow.de:7890/node/info

It works when replacing the domain with the underlying ip. Please check what is wrong.

Hi, @BloodyRookie!
Tests for the node do not work.
https://supernodes.nem.io/details/938

NEM node and servant works.
http://82.202.162.62:7890/node/extended-info
http://82.202.162.62:7880/nr/metaData

What is the problem?

Also please check my z1 node http://195.54.162.238:7890/node/extended-info

FYI @BloodyRookie is having issues logging in to our forum. I will be working on a solution today. Please hang on while we get this issue figured out.

Seems the node recovered.

NIS was booted with the wrong key. Please check your config.

now key is right?

Looks ok now. Please wait for the new tests.

Wow, your node pass Computing power test so fast! less then a second!
What VPS provider and config you using?))