NEM Supernode Rewards Program

Blog Posts
#2026

Dear BloodyRookie.

I sended
change alias SHINSHI INTERNATIONAL PATENT OFFICE to OPIS
transaction hash:01bc17cd1d5d93a24349042039b8065aef311213f25260089d384cdc19da31f9

But did not work yet, I think.
is it any mistakes?

#2027

i changed it manually.

#2028

I am still having problems with my supernode. This has been going on for around a week.
The last test failed on the height and chain tests.
A couple of tests passed, but I am not passing enough of them to qualify for the payouts.
I am now running the 0.6.95 version, which has made no difference.
I have restarted nis several times.
https://nemnodes.org/nodes/ shows my node, and the height test works instantly.
Advice appreciated

#2029

Upgrade to your server to 4GB and give NIS 2800M in the startup script.

1 Like
#2030

I am running it on Windows 10.
There is 16gb ram if that is relevant?

In ā€˜runNis.batā€™ - java -Xms512M -Xmx1G Should I change these values?

#2031

Yes, if you have 16GB ram, you can change the startup params to -Xms3G -Xmx3G and NIS will be happy.

#2032

Ok thanks I have just done that - fingers crossed :slight_smile:

#2033

Hi,

SN https://supernodes.nem.io/details/541 gets Fail many times.

http://185.133.192.191:7890/chain/height
http://185.133.192.191:7880/nr/metaData
http://185.133.192.191:7890/node/extended-info

Any thoughts why?
Thanks in advance

#2034

Probably a 2GB supernode. Please upgrade to at least 4GB and adjust the NIS startup script to use 2800MB heap.

#2035

Hi BloodyRookie, have 6GB vps and set 3G/3G in runNis bat file 3 days ago.

Maybe this is a problem with incorrect delegated public/private key?

#2036

Indeed. I deactivated the old db entry and added a new one:

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

#2037

BloodyRookie, thanks you!

#2038

thank you.

#2039

Hello everyone,

Im having connections problems at the rounds checks. The server is online and serving as a remote harvester for 2 other people. But the test fails on the page,

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

2017-12-29 17:07:36.642 INFO 2 harvesters are attempting to harvest a new block. (org.nem.nis.ld.gah cH)
2017-12-29 17:07:37.080 INFO entering /time-sync/network-time [190.56.75.78] (org.nem.nis.controller.interceptors.AuditInterceptor preHandle)
2017-12-29 17:07:37.081 INFO exiting /time-sync/network-time [190.56.75.78] (org.nem.nis.controller.interceptors.AuditInterceptor afterCompletion)
2017-12-29 17:07:37.568 INFO received 1 blocks (2 transactions) in 179 ms from remote (89500 Ī¼s/tx) (org.nem.nis.sync.BlockChainUpdater c)
2017-12-29 17:07:37.644 INFO 2 harvesters are attempting to harvest a new block. (org.nem.nis.ld.gah cH)
2017-12-29 17:07:40.044 INFO 2 harvesters are attempting to harvest a new block. (org.nem.nis.ld.gah cH)
2017-12-29 17:07:42.743 INFO 2 harvesters are attempting to harvest a new block. (org.nem.nis.ld.gah cH)
2017-12-29 17:07:42.773 INFO validated 1 blocks (2 transactions) in 5203 ms (2601500 Ī¼s/tx) (org.nem.nis.sync.BlockChainUpdateContext fz)
2017-12-29 17:07:42.773 INFO new blockā€™s score: 119770424750693 (org.nem.nis.sync.BlockChainUpdateContext a)
2017-12-29 17:07:42.798 INFO chain update of 1 blocks (2 transactions) needed 25 ms (12500 Ī¼s/tx) (org.nem.nis.sync.BlockChainUpdateContext fz)

Can you please help me out, thanks

#2040

Maybe the server was offline and you recently started it? It will pass all tests next round.

#2041

Thanks for your response.

I have my nano wallet linked to it, and it shows my balance etc. Its been online for the last few months, I only restart the OS after a new NEM version is intalled. After I notice the problem I restarted it around 4am, and everything seems fine in the log.
But it has already failed two tests today. The connection port looks fine, Im thinking maybe there are more transactions now and the servers needs more CPU or RAM??

thanks again

My NIS server is not synchronizing, claiming the nodes as blacklisted
#2042

As i said, it will pass the next round. However, if your supernode got less than 2 GB, I would suggest upgrading it to 4GB and adjusting the startup script to give NIS 2800MB heap.

#2043

Thank you sir!

#2044

I switched from NCC to nano wallet, but the reward check came to fail. I tried various investigations because I do not know the cause. One of the reasons is that since the delegation public key has changed even at the same address, I heard that it is necessary to change the setting manually now.
In that case, how can I ask for it?
Should I just write SN names and public keys directly in this forum? Or should I contact someone?

IP address and delegation public key are here.
http://153.122.60.153: 7890/node/info

Here is the server name and the review status
https://supernodes.nem.io/details/283

This is the old delegation public key we used with NCC.
6d2ef1b7aa9cb974fa668a8b12c4d056286e37fc3dd06d7d54b46433d77c0894

#2045

Send a message to NALICE-PFLZQR-ZGPRIJ-TMJOCP-WDNECX-TNNG7Q-LSG3 from the account you used to enroll that supernode. Message should be something like ā€œplease change the public key to 6d2ef1b7aa9cb974fa668a8b12c4d056286e37fc3dd06d7d54b46433d77c0894ā€. I will then disable the old supernodes db entry and add a new one.