NEM Supernode Rewards Program

Not sure if windows is a good choice for an OS for a supernode. I use debian or ubuntu. So maybe the problem is that windows is not so good with regards to memory. Any chance to switch to an nix* system?

I’ll try. I did not work with other systems. What do you advise?

why didn’t it work? Should work with the most linux system.

Ok! Should I increase the RAM size? Will this help?

2GB should be enough. But generally, the more RAM you have the better it is. The RAM given to NIS can be configured in the startup script.

Ubuntu 64 or 32 Bit? Which is better?

or Debian?

Always 64 bit operating systems!
I use debian 8.

1 Like

Thanks!))

Here is the current nis-0.log, as it failed again:
superNode: https://supernodes.nem.io/history/search/LandofNode

2017-11-06 15:34:33.013 WARNING forcibly aborting request to http://go.nem.ninja:7890/node/cysm (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:34:33.013 WARNING forcibly aborting request to http://san.nem.ninja:7890/node/cysm (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:34:33.013 WARNING forcibly aborting request to http://nijuichi.nem.ninja:7890/node/cysm (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:34:33.013 WARNING forcibly aborting request to http://62.75.251.134:7890/node/cysm (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:34:35.621 INFO entering //node/extended-info [5.196.225.192] (org.nem.nis.controller.interceptors.AuditInterceptor preHandle)
2017-11-06 15:34:35.622 INFO exiting //node/extended-info [5.196.225.192] (org.nem.nis.controller.interceptors.AuditInterceptor afterCompletion)
2017-11-06 15:34:36.741 INFO entering //chain/height [5.196.225.192] (org.nem.nis.controller.interceptors.AuditInterceptor preHandle)
2017-11-06 15:34:36.742 INFO exiting //chain/height [5.196.225.192] (org.nem.nis.controller.interceptors.AuditInterceptor afterCompletion)
2017-11-06 15:34:39.157 INFO entering //node/peer-list/all [5.196.225.192] (org.nem.nis.controller.interceptors.AuditInterceptor preHandle)
2017-11-06 15:34:39.161 INFO exiting //node/peer-list/all [5.196.225.192] (org.nem.nis.controller.interceptors.AuditInterceptor afterCompletion)
2017-11-06 15:34:52.990 INFO entering /time-sync/network-time [74.71.181.170] (org.nem.nis.controller.interceptors.AuditInterceptor preHandle)
2017-11-06 15:34:52.990 INFO exiting /time-sync/network-time [74.71.181.170] (org.nem.nis.controller.interceptors.AuditInterceptor afterCompletion)
2017-11-06 15:34:52.990 INFO exiting /time-sync/network-time [74.71.181.170] (org.nem.nis.controller.interceptors.AuditInterceptor afterCompletion)
2017-11-06 15:35:28.374 INFO entering /node/sign-of-life [78.46.210.129] (org.nem.nis.controller.interceptors.AuditInterceptor preHandle)
2017-11-06 15:35:33.334 WARNING forcibly aborting request to http://62.75.171.41:7890/node/sign-of-life (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:35:33.334 WARNING forcibly aborting request to http://hachi.nem.ninja:7890/node/sign-of-life (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:35:33.334 WARNING forcibly aborting request to http://jusan.nem.ninja:7890/node/sign-of-life (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:35:33.334 WARNING forcibly aborting request to http://104.238.161.61:7890/node/sign-of-life (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:35:33.335 WARNING forcibly aborting request to http://108.61.182.27:7890/node/sign-of-life (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:35:33.335 WARNING forcibly aborting request to http://209.126.98.204:7890/node/sign-of-life (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:35:33.335 WARNING forcibly aborting request to http://108.61.168.86:7890/node/sign-of-life (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:35:33.335 WARNING forcibly aborting request to http://nijuichi.nem.ninja:7890/node/sign-of-life (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:35:33.335 WARNING forcibly aborting request to http://san.nem.ninja:7890/node/sign-of-life (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:35:33.335 WARNING forcibly aborting request to http://62.75.251.134:7890/node/sign-of-life (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:35:33.335 WARNING forcibly aborting request to http://62.75.163.236:7890/node/sign-of-life (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:35:33.336 WARNING forcibly aborting request to http://go.nem.ninja:7890/node/sign-of-life (org.nem.core.connect.HttpMethodClient lambda$sendRequest$2)
2017-11-06 15:35:33.337 WARNING Timer BROADCAST raised exception: java.util.concurrent.CancellationException
java.util.concurrent.CompletionException: java.util.concurrent.CancellationException
_ at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)_
_ at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)_
_ at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:593)_
_ at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)_
_ at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)_
_ at java.util.concurrent.CompletableFuture.cancel(CompletableFuture.java:2265)_
_ at org.nem.core.connect.HttpMethodClient$HttpMethodClientFutureCallback.cancelled(HttpMethodClient.java:216)_
_ at org.apache.http.concurrent.BasicFuture.cancel(BasicFuture.java:150)_
_ at org.apache.http.concurrent.BasicFuture.cancel(BasicFuture.java:157)_
_ at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.executionCancelled(DefaultClientExchangeHandlerImpl.java:112)_
_ at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.cancel(AbstractClientExchangeHandler.java:432)_
_ at org.apache.http.client.methods.AbstractExecutionAwareRequest.abort(AbstractExecutionAwareRequest.java:90)_
_ at org.nem.core.connect.HttpMethodClient.lambda$sendRequest$2(HttpMethodClient.java:129)_
_ at java.util.concurrent.CompletableFuture.uniAccept(CompletableFuture.java:656)_
_ at java.util.concurrent.CompletableFuture$UniAccept.tryFire(CompletableFuture.java:632)_
_ at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)_
_ at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)_
_ at org.nem.core.async.SleepFuture$1.run(SleepFuture.java:24)_
_ at java.util.TimerThread.mainLoop(Timer.java:555)_
_ at java.util.TimerThread.run(Timer.java:505)_
Caused by: java.util.concurrent.CancellationException
_ at java.util.concurrent.CompletableFuture.cancel(CompletableFuture.java:2263)_
_ … 14 more_
_ (org.nem.core.async.NemAsyncTimerVisitor notifyOperationCompleteExceptionally)_
2017-11-06 15:35:43.763 INFO /chain/last-block height:1359676 signer:NAOKZIK4V7HK57ACJETHNE7K2IKPAJ6VOK32IM54 (org.nem.nis.controller.zwd bP)
2017-11-06 15:35:52.125 INFO entering //node/extended-info [5.196.225.192] (org.nem.nis.controller.interceptors.AuditInterceptor preHandle)
2017-11-06 15:35:52.126 INFO exiting //node/extended-info [5.196.225.192] (org.nem.nis.controller.interceptors.AuditInterceptor afterCompletion)

Dear BR

I sent following messages just now.

  1. Please disable supernode NoiseR5
  2. enroll 153.122.87.2 NoiseR8
    c039b6e16172a316c9c9ab704e5719d6a42cbb228b99bed92823fd31b464b9e0

Please respond to that.
If there is problem, please send me trouble message.

Thank you.

Looks like serious connection problems. Can you provide the full log file?

Dear BR

I send to you following E-mail to you.
Please help me!

thank you.

E-Mail? I didn’t receive an email from you.

Done, new entry is

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

Hello BR

Sorry, not E-mail. Message to forum right.

Thanks.

I think I will just create a new droplet.

Can I just switch out IPs once it is up and running, or do I need to reenroll
my supernode with delegated key and everything?

If only the ip changes, you can send a change message to the server. See first post of this thread.

ok made request to change IP/alias …