NEM Supernode Rewards Program


#2845

I don’t received the payment from round 4649-4652 (khellendros).

Thanks


#2846

Uff, indeed seems the previous round already suffered from the same problems :confused:
Will address that in a bit.


#2847

Missing payouts for rounds 4649 - 4652:

payouts.pdf (53.1 KB)


#2848

Hi, any adjustments that can be made to prevent computing power failures? Has been ~1000 ms consistently, but now intermittently can go to 6000+ and failing. 4gb ram node.


#2849

Might be the garbage collector doing its work. You might want to restart NIS or upgrade to 8GB and use G1 garbage collector.


#2850

I’ve just restarted NIS and increased memory allocated to Java to 3200 MB from 3072 MB. Would removing the garbage collector line from the nis startup script help if it’s caused by GC?


#2851

I don’t think that will help since the node is probably using swap memory which is very slow.

Not sure you mean “removing the garbage collector”.


#2852

There was some text you asked me to add ending in GC.txt in the nisStart.sh file a while ago, I meant starting NIS without the garbage collector text.


#2853

That may be the use of the G1 garbage collector, i can’t tell without seeing the actual nisStart.sh.
Restarting NIS probably already has the GC.txt overwritten, else i could have taken a look at it to see how much your NIS was under pressure memorywise.
Removing the additional startup param for the garbage collector only results in the use of the default garbage collector which is not better.
Increasing memory is probably the best option.


#2854

Hi, the additional text at the end of the startup script was as below:

-XX:+UseG1GC -XX:MaxGCPauseMillis=200 -XX:+PrintGC -Xloggc:"./gc.txt"

I presume this is the G1 collector.


#2855

Yes. So unless your provider is the culprit of poor computing power results, the only option would be to increase memory.


#2856

It seems that the balance check did not work.
#1782622#1782821

It seems to be restored now.


#2857

the problem I think does not fixed yet


#2858

Yeah, I observed exactly the same problem - it failed for balance in round #4679 and #4680, even if balance is - of course - right (over 3mio XEM). If this happened (happens) only for a part of supernodes, I hope it will be recalculated for the right reward after solving this issue.

And anyway, about the rewards - I’m still waiting for the payout for rounds #4673-#4676. It should came yesterday (2019-03-14) around 14:00-15:00 GMT, but nothing arrived. Did anybody has the same experience ?


#2859

Reason for the failures were that i needed to restart the local NIS on the node rewards master. I will check on weekend which nodes suffered from that problem and issue the missing payouts.


#2860

why some nodes had paid at 4677-4680 for 838?
seems stuck at number 167


#2861

Are there any recommendations on providers for hosting a node? Preferably ones with pre-configured nodes if possible, I think I vaguely remember ctl.io have a pre-installed supernode server which just requires configuration with your settings. I’ve also seen recommendations of people recommending vultr.


#2862

Hi, I do not know if you know the page. Here you have an overview of all used ISP´s (NEM Blockchain).

" https://nodeexplorer.com/ "


#2863

Thanks, looks like vultr is most popular.


#2864

not sure about OS though, seems like there’s a lot of options in vultr, like debian, ubuntu, fedora, centos etc. Thinking of going for the 8GB to future proof it. VC2 $40 per month. Is there still a tutorial available, I used Pauls one last time, not sure if it’s still valid though.