NEM Supernode Rewards Program

Those sporadic failures indicate that the connection to the server could not be made. And that is a failure, isn’t it? If the failure occurs just as often as for all other nodes, it will level out in the long run (since the payout is always 140k per day). If the nodes has more of those failures than other nodes, it means the connection is not as stable as for other nodes and that is punished.

I don’t get it. If this mean that node lost connection, that this mean?

How long all tests take time?

For each test, the master connects to the node. If that fails, the test can’t be performed. Connect failure happen from time to time, every node has such failures sometimes.

Here are the missing payouts from two weeks ago where i had to restart the NIS on the node-rewards server:

payouts.pdf (34.9 KB)

Thank you :grinning:

Please upgrade your supernode to version 0.6.96. This upgrade is mandatory.

1 Like

hi,
supernode http://88.99.87.132/ “croissant” is going to maintenance upgrade now.
There are 47 harvesters, please restart harvesting later.

1 Like

Hello @BloodyRookie!

Can you please understand what has happened here and why i missed the reward?!

https://supernodes.nem.io/archive/947/3828

Screenshot%20at%20Aug%2014%2009-38-19|690x444

Those sporadic failures do occur, the internet is not 100% stable, everyone gets those errors. The usual problem is that the master could not connect to the node.

i see. in this case, is there a way to get the reward that was missed because of this sporadic failure?

No, it will level out in the long run.

z1 and z4 nodes failed tests
message “NIS_ILLEGAL_STATE_LOADING_CHAIN”
reboot them twice, it didn’t help

Just means that you need to let the node load the chain. That might need quite a while depending on the node specs. Rebooting is counter productive since it needs to start loading the entire chain again.

i reboot them august 12. two days ago. guess it stuck :thinking:

Hmm… in that case, maybe you can upload the log?

ok, there i can get it?

root/nem/nis/logs?

its it?

if you run NIS as root, yes

The node seems to be super slow, it needs 22 minutes to reach the point where is starts to load the chain. A fast node needs 5 seconds for that. It then needs more than 12 hours to load the chain to height 1230001 (that is where the logs ends). Probably would have needed another 2 days to load the rest of the chain.

Honestly, there is something wrong with the supernode. What are the specs of the node?

4Gb ram, 4 cores intel i5 3ghz cpu and 25 Gb SSD storage

1 Like