NEM Supernode Rewards Program

Blog Posts
#2967

Give it more time.

#2968

@BloodyRookie the public key was wrong the first time - now it is corrected. Do we have to send the enroll message again?
http://107.150.46.98:7890/node/extended-info

#2969

also is there a way to make it https ?

#2970

looks like all tests failing -
https://supernodes.nem.io/details/1090

any ideas to troubleshoot?

#2971

What does the correct public key look like?

#2972

This is the correct public key:
952b2fdc42e2a674a179175d67e0087ce7708f509f5aabbc557c0ff124adb852

We just corrected it now - the enroll message was sent before the correction.
Just clarifying whether we need to send the enroll message again

#2973

That’s the public key i see in the db, so if you didn’t use it in the enroll message i wonder how it can be in the db ^^
What is the hash of the enroll tx?

#2974

Looks to me like there is something wrong with NIS, is it not running?

#2975

No - I sent the correct public key in the enroll message - there was some error while setting up the server which we corrected after.
here is the tx hash:
5d6c2ba203870fccace3361752e1883cc5071615946cf5996111f63b86bfcab2

#2976

Hi Team,

I am getting below error and my node crashed. Could not figure out cause for crash. Any insight will be helpful

2019-08-22 15:17:29.837 INFO synchronizing with Node [[c=#86c0e9]jusan[/c] ] @ [jusan.nem.ninja] (org.nem.peer.services.NodeSynchronizer b)

2019-08-22 15:17:30.093 WARNING Timer SYNC raised exception: java.lang.IllegalStateException: Request cannot be executed; I/O reactor status: STOPPED

java.util.concurrent.CompletionException: java.lang.IllegalStateException: Request cannot be executed; I/O reactor status: STOPPED

at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)

at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)

at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1629)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

#2977

You need to restart your NIS, it was probably out of memory.

#2978

Thankyou!!!
Yes Cache Memory was full .After clearing cache it worked.
sync; echo 1 > /proc/sys/vm/drop_caches

#2979

Hi Team,

My Test results are failing with Chain-part and Responsiveness (8/10). Please share details what needs to be checked to fix these errors.

Why Chain hash is not matching. And why is Responses/Requests 8/10

Link to check health report: https://supernodes.nem.io/details/1090

#2980

how much memory does the vps have and how much do you give to the NIS java process upon start?

#2981

Its 1GB min and 2 GB MAX.
Now Report is failing with Chain Height and Chain Hash. Please let me know what needs to be done to resolve this issue.

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

#2982

That is not enough. I recommend at least 4GB, i.e. -Xms4G -Xmx4G, or better 8GB.

#2983

Thank you for help. I will increase and test it.

#2984

Thank you Again, BR!!
After increasing Heap memory to 6GB, all test cases are passing

#2985

Hi @BloodyRookie . Please help to change IP addresses of these supernodes:

  1. change ip 207.148.126.147 to sn01.cyberblox.my
  2. change ip 45.63.27.20 to sn02.cyberblox.my
  3. change ip 108.61.166.217 to sn03.cyberblox.my
  4. change ip 45.77.63.201 to sn04.cyberblox.my

And please also change the alias for the supernodes:

  1. change alias cyberblox_sn_service1 to cbx-sn-01
  2. change alias cyberblox_sn_service2 to cbx-sn-02
  3. change alias cyberblox_sn_service3 to cbx-sn-03
  4. change alias cyberblox_sn_service4 to cbx-sn-04

All messages have been sent to NAFUND address 3 days ago.

#2986

Are the corresponding main accounts multisigs?
Can you paste the hashes of the transactions for the changes?