NEM Supernode Rewards Program

Blog Posts
#2046

Thank you so much, I count on you. I have just sent a message.

#2047

New entry is

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

#2048

Hi , BloodyRookie.

I changed 3 SNs 2GB to 8GB,and changed nis startupscript to Xmx5G,Xms5G. 24hrs ago.
they did not change IP-address,deligated-keys,and so on.
I think they works fine,isnā€™t it?
http://157.7.197.62:7890/node/extended-info/
http://157.7.197.62:7880/nr/metaData

http://157.7.198.84:7890/node/extended-info/
http://157.7.198.84:7880/nr/metaData

http://157.7.196.200:7890/node/extended-info/
http://157.7.196.200:7880/nr/metaData

but NEM node reward says fails. have I any problems?or just be waiting?
https://supernodes.nem.io/details/754 755 756

#2049

The public key displayed in the links above is different from the public key that is in the database. For example
http://157.7.197.62:7890/node/extended-info/
shows
b5a0564d757a31d58e6c093f3f86206a0c5df078714f4e9c0b529cada3a0a4df
which is your main accountā€™s public key while in the database is see
b973cb6b2659cd6d33cd60b14d8e9c7c89e0d09f4cc5a8d3c7af6a688b4cbef2
which is the delgated public key of the account. Donā€™t use the main private key on the supernode, that is risky!

So change the config and use the delgated private key please.
Same goes for the other two servers of yours.

#2050

I see,
I check it soon. thank you.

#2051

Hi @BloodyRookie - wanted to add my new super node in.
My enroll txHash is d795a292f97f9108301868090cbb54d166a351ec7929c80a0808fc967ddfe6e6, can you please check if the TX is fine?

#2052

It was successfully judged and passed on the correctly registered node. Thank you very much.

#2053

Hi, neverminded, was the change (to -Xms3G -Xmx3G) successful for you ? There is absolutely the same problem by me ā€“ I have ā€œrock solidā€ node, passed all the test for couple of months, 16GB RAM (just on Linux), and last week I have repeatedly troubles with Height and Chain part in the measuring (and thus my node is failing the tests). Upgrade from 0.6.93 to 0.6.95 doesnā€™t solve the situation.

#2054

I guess it was since he didnā€™t state the opposite :slight_smile:

#2055

I added the new entry:

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

#2056

Hi @BloodyRookie I have just sent to your NEM account message to change my NEM supernode ip.
So please change ip 185.185.41.105 to 185.185.40.67

Thanks!

#2057

Was changed automatically by the bot.

1 Like
#2058

Version 0.6.95 is available:

Please upgrade your supernode to have at least 4GB RAM. Generally the more RAM the supernode has, the better it is. Also donā€™t forget to adjust the java startup params. If you have 4GB available for the node you should set

-Xms2800M -Xmx2800M

in the startup script (which is nix.runNis.sh by default)

1 Like
#2059

@BloodyRookie

New enroll txHash is 29023810ddc98dfadaa89d3ad7ad444ef21387b7cdcf25024a2e3a45fd784d59 for another new node ninja2016, can you please check if the TX is fine?

  • thanks for the earlier addition for ninja3. it works.
#2060

New entry is

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

#2061

@BloodyRookie
Hey BR. My 103.192.177.252 has also only 2 GB RAM and is failing again and again
I just asked HostUS to give me another node with 4 or 8 GB.
It may take a day until it is paid and running and Iā€™ve a new IP.
Thanks

#2063

I thought that was the nisStart.sh. Then I know why this does not work for me

#2064

i donā€™t know about your setup on your supernode. How do you start NIS?

#2065

Hello, how i can solve the problem with Chain height?
I have that problem 4 times in a row. And last time https://supernodes.nem.io/archive/839/2960 i had really strange value of Chain height. But last check of chain height in logs looks like
2018-01-04 09:27:21.510 INFO block height: 1444724 (org.nem.nis.service.PushService m)
2018-01-04 09:27:21.510 INFO isLastBlockParent? true; last block height: 1444723; hash: 012e6ff56ef3434575ecd1df0b04c701b69028eabcde83fd9b6f7d2bd0d732e6 (org.nem.nis.BlockChain a)

What i did wrong>?

#2066

See my post above: