NEM Supernode Rewards Program

Blog Posts
#2782

What is the supernode’s name?

#2784

I’ve changed the value to 2400 now, and have just restarted the server so chain is loading.

#2785

Would leave 2500, maybe try a more responsive garbage collector via adding
-XX:+UseG1GC -XX:MaxGCPauseMillis=200 -XX:+PrintGC -Xloggc:"./gc.txt"
to the startup command.

#2786

Thanks. It’s not something I’ve done before, but does this look right?

I’ve edited the nisStart.sh file with vi and will amend as follows, just need to check the new garbage collector line is in the right place

cd nis
java -Xms2500M -Xmx2500M -cp “.:./:…/libs/” org.nem.deploy.CommonStarter
-XX:+UseG1GC -XX:MaxGCPauseMillis=200 -XX:+PrintGC -Xloggc:"./gc.txt"
cd -

#2787

Looks ok to me. If it starts, then everything is fine.

#2788

thanks, I’ve made the changes and it started correctly. Will monitor and see how it goes.

#2789

It’s still failing on computer power. Is there anything else that can be done. Java is still on 2500xms 2500xmx. They were both previously 2800. Max ram is 4gb, swap is 1gb.

#2790

Can you try the following command:
time echo "scale=2000; 4*a(1)" | bc -l
(Might have to install bc for that)

#2792

2 seconds is fast enough to pass the computational test. Really don’t know why your node has such problems with the test :confused:

#2793

I’ve changed Java xms ro 2048 and it seems to have resolved the computing power, but is now failing on chain part and height. Any idea how to resolve this?

#2794

Failing on chain part means NIS is not synced, probably due to lack of memory. Lowering xms value does not help.

#2795

Hi @BloodyRookie

Excuse me for interrupting your work.

I built a new supernode satoshi.N.
The node is successfully accepted and listed here https://supernodes.nem.io/details/1042 .

But I got a problem, which is that the balance of the account is not properly reflected on the rewarding system;
the account has more than 3M XEM, but the rewarding system shows it has 0 XEM.

Do kyou know what happens and how to solve it?

This is the first time I have got this kind of error.

related information is here

regards

#2796

The delegated public key used for enrolling the supernode is

8319cf67b959ad4b486f986f6d36a694733174d43c7e4a2fed29307e68c729c1

but the real delegated public key is

267c15e654c158e1ff906ad4ba772902191fd3d1e54ffebe367f48fe25325465

which can be seen here

http://chain.nem.ninja/#/account/NC4H3E-B6G4ZO-JAT3ID-4XGDKT-U6LUVJ-AMJRLJ-WHLE/0

So you used the wrong delegated public key for enrolling.

#2797

Hi BloodyRookie
Sometimes my supernode stopped with “chain height” problem in 2019.
when I reboot and restart NIS and servant, it will be “Pass” soon and works well in a while.
but next 48h or more than hours, it will stop and Fail again.
what should I do?
(By the way, I set “nix.runNis.sh” params -Xms6G -Xmx6G)

https://supernodes.nem.io/details/436

#2798

Does the vps have 8GB? If yes i think giving nis 6GB is too much, try 5GB, e.g. -Xms5G -Xmx5G. Also use G2 garbage collector, -XX:+UseG1GC -XX:MaxGCPauseMillis=200.

#2799

Thank you.I’ll try it.

#2800

@BloodyRookie Thank you for your reply.

My customer misunderstood which delegated public key to use, and this is already fixed.

Thank you again.

#2801

Hi. Please change IP of my supernode.

change ip 160.16.140.161 to 133.167.106.40.

I already sent enroll message to NAFUND address,
the tx hash:
e15b011f6bdc0234b7a6c30ec786d05e4fdaf65d7ef4e9e6c7150da9b1dc6e83
Thanks!

#2802

You sent an enroll message instead of an ip change message. Anyway i changed it in the db.

#2803

How is it fixed? Did he enroll with new delegated public key, new ip and new name?