Anybody with low power computer (or even single board computer) running NIS/NCC?


Where is the problem?

Download latest nis and ncc version from http://bob.nem.ninja/ (now: nis-ncc-0.4.34.tgz).
- Extract it
- run nix.runNis.sh and wait till its done ("ready to server")
- run nix.runNcc.sh and wait till its done ("ready to serve")
- optional: forward the port (defalut 7890) in your router to the cubietruck local IP
- go to the webinterface: http://CUBIETRUCK-IP:8989/ncc/web/index.html

Edit: Im curious if NXT and NEM will run without problems at the same time.


When i run nix.runNis.sh and i see "Nem Infrastructure Server is ready to serve" i'm not able to do anything.
I must wait more time?

Sorry, but i'm a newby in linux  :)

Ok, I see.
Well if you are running a gui (Xfce e.g.) then you have to open another terminal and "sh nix.runNcc.sh".
If you are not running a gui then you have to switch to another terminal by CTRL+ALT+F2 (or F3-F7) and do "sh nix.runNcc.sh" from there.

My host is wrong? or/and command? :

root@cubieez:~# sudo package/nix.runNis.sh
sudo: unable to resolve host cubieez
/root/package/nix.runNis.sh: line 3: cd: nis: No such file or directory
/root/package/nix.runNis.sh: line 4: java: command not found
/root/package/nix.runNis.sh: line 5: cd: OLDPWD not set

I enable the box on properties nis and ncc: "make the file executable"

I will need to study many days for lubuntu on google search…

Usually you start NIS like this:
sh /path-to-NEM-BETA-directory/nix.runNis.sh

In general it doesn't make sense to use "sudo", if you are logged in as "root". ("Sudo" gives a normal user root privileges.)

This: "/root/package/nix.runNis.sh: line 4: java: command not found"
sounds like you didn't set the java environment variables?

You could try this (you probably have to look at the used path: /opt/jdk1.8.0_06)
[code]-> most of java based application


Ok, I see.
Well if you are running a gui (Xfce e.g.) then you have to open another terminal and "sh nix.runNcc.sh".
If you are not running a gui then you have to switch to another terminal by CTRL+ALT+F2 (or F3-F7) and do "sh nix.runNcc.sh" from there.


I'm using putty from my windows pc, so i start Nis (until "ready to serve" and open new session.
But now when i run Ncc i see:

[code]...
22:07:45 WARNING Timer TIME SYNCHRONIZATION raised exception: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException
...
[/code]

If i go with mi browser to the port 8989 i see the client interface perfectly but on the top there is "Nis is not available"

Sorry, I don't know the reason for this warning.

Maybe it helps, if you provide more context of the log.

It is continuosly this:

22:41:37 INFO exiting /ncc/api//info/nis/chain/height [192.168.0.2] (org.nem.ncc.controller.interceptors.AuditInterceptor afterCompletion)<br />22:41:37 INFO entering /ncc/api//info/nis/chain/height [192.168.0.2] (org.nem.ncc.controller.interceptors.AuditInterceptor preHandle)<br />22:41:39 SEVERE Http Status Code 500: java.net.SocketTimeoutException (org.nem.core.connect.ErrorResponse &lt;init&gt;)<br />22:41:39 SEVERE Http Status Code 500: java.net.SocketTimeoutException (org.nem.core.connect.ErrorResponse &lt;init&gt;)<br />22:41:39 INFO exiting /ncc/api//info/nis/chain/height [192.168.0.2] (org.nem.ncc.controller.interceptors.AuditInterceptor afterCompletion)<br />22:41:39 INFO entering /ncc/api//info/nis/chain/height [192.168.0.2] (org.nem.ncc.controller.interceptors.AuditInterceptor preHandle)<br />22:41:40 WARNING Timer TIME SYNCHRONIZATION raised exception: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException<br />java.util.concurrent.CompletionException: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException<br />&nbsp; &nbsp; &nbsp; &nbsp; at java.util.concurrent.CompletableFuture.internalComplete(CompletableFuture.java:205)<br />&nbsp; &nbsp; &nbsp; &nbsp; at java.util.concurrent.CompletableFuture$ThenApply.run(CompletableFuture.java:723)<br />&nbsp; &nbsp; &nbsp; &nbsp; at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:193)<br />&nbsp; &nbsp; &nbsp; &nbsp; at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2361)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.nem.core.connect.HttpMethodClient$HttpMethodClientFutureCallback.failed(HttpMethodClient.java:199)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:130)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.connectionRequestFailed(DefaultClientExchangeHandlerImpl.java:318)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.access$100(DefaultClientExchangeHandlerImpl.java:63)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl$1.failed(DefaultClientExchangeHandlerImpl.java:364)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:130)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager$InternalPoolEntryCallback.failed(PoolingNHttpClientConnectionManager.java:474)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:130)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.nio.pool.RouteSpecificPool.timeout(RouteSpecificPool.java:170)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.nio.pool.AbstractNIOConnPool.requestTimeout(AbstractNIOConnPool.java:546)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.timeout(AbstractNIOConnPool.java:779)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.impl.nio.reactor.SessionRequestImpl.timeout(SessionRequestImpl.java:177)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processTimeouts(DefaultConnectingIOReactor.java:212)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:157)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:189)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.doExecute(CloseableHttpAsyncClientBase.java:67)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.access$000(CloseableHttpAsyncClientBase.java:38)<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:57)<br />&nbsp; &nbsp; &nbsp; &nbsp; at java.lang.Thread.run(Thread.java:745)<br />Caused by: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException<br />&nbsp; &nbsp; &nbsp; &nbsp; at org.nem.core.connect.HttpMethodClient$HttpMethodClientFutureCallback.wrapException(HttpMethodClient.java:204)<br />&nbsp; &nbsp; &nbsp; &nbsp; ... 20 more<br />Caused by: java.net.SocketTimeoutException<br />&nbsp; &nbsp; &nbsp; &nbsp; ... 12 more<br /> (org.nem.core.async.NemAsyncTimerVisitor notifyOperationCompleteExceptionally)<br />22:41:43 SEVERE Http Status Code 500: java.net.SocketTimeoutException (org.nem.core.connect.ErrorResponse &lt;init&gt;)<br />22:41:43 SEVERE Http Status Code 500: java.net.SocketTimeoutException (org.nem.core.connect.ErrorResponse &lt;init&gt;)<br />

I also see this when i run ncc:

22:44:28 INFO Acquiring exclusive lock to lock file: /root/nem/ncc.lock (org.nem.core.deploy.CommonStarter tryAcquireLock)<br />22:44:28 INFO Analyzing meta data in &lt;nem-core__V0.4.34-BETA.jar&gt; (org.nem.core.metadata.JarFacade &lt;init&gt;)<br />22:44:28 INFO Meta data title &lt;NEM Community Client - NCC&gt;, version &lt;0.4.34-BETA&gt; (org.nem.core.metadata.JarFacade &lt;init&gt;)<br />22:44:28 INFO Starting embedded Jetty Server. (org.nem.core.deploy.CommonStarter main)<br />22:44:31 INFO Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@3d9750: startup date [Sat Nov 22 22:44:31 CET 2014]; root of context hierarchy (org.springframework.context.annotation.AnnotationConfigApplicationContext prepareRefresh)<br />22:44:37 WARNING unable to load NCC configuration: java.io.FileNotFoundException: /root/nem/ncc/ncc.cfg (No such file or directory) (org.nem.ncc.NccMain loadConfigurationStream)<br />22:44:37 WARNING unable to load the accounts cache from disk because it is empty (org.nem.ncc.cache.AccountsFileRepository tryLoad)<br />

Ok I don't know the reason for the "WARNING Timer TIME SYNCHRONIZATION". Lets wait for a dev.

The warning about the missing NCC configuration file and accounts cache is because you probably started it the first time, and it just not there yet… :wink:
The configuration file will be created. And you have to create a wallet, then this won't be displayed again.


@gimre:
Im running it with the default settings.

What is the best way to measure the cpu load for you without gui with debian 7?

install "top" or "htop"

just write at terminal "htop" or "top" command and it'll show you the overall processes and cpu / ram / and other systems stats.


Ok, I see.
Well if you are running a gui (Xfce e.g.) then you have to open another terminal and "sh nix.runNcc.sh".
If you are not running a gui then you have to switch to another terminal by CTRL+ALT+F2 (or F3-F7) and do "sh nix.runNcc.sh" from there.

I'm using putty from my windows pc, so i start Nis (until "ready to serve" and open new session.
But now when i run Ncc i see:
[code]...
22:07:45 WARNING Timer TIME SYNCHRONIZATION raised exception: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException
...
[/code]
If i go with mi browser to the port 8989 i see the client interface perfectly but on the top there is "Nis is not available"


Im not so sure if the Devs implemented a feature in which you dont need the correct clock synchronization( if clock have wrong hour and date, it was supposed to not work).

As the little machine are not so powerful, I notice my windows machine ( AMd 7850K APU 4 core @ 4 GHZ) takes, sometimes, 2 or 3 minutes to change the red strip message from 127.0.0.1:8989 to the yellow message.

By the way... the modens Door 7890 are directed to your machiane IP?

As they are making modifications, this could be a clue about whats happening.

:)

Thanks parana.

According to htop, the CPU load while NIS and NCC are running is often at 100 % (both cores).
Memory usage: 1250 of 1999 MB.

[url=http://postimg.org/image/7fli4oe0d/]


Usually you start NIS like this:
[code]sh /path-to-NEM-BETA-directory/nix.runNis.sh[/code]

In general it doesn't make sense to use "sudo", if you are logged in as "root". ("Sudo" gives a normal user root privileges.)

This: "/root/package/nix.runNis.sh: line 4: java: command not found"
sounds like you didn't set the java environment variables?

You could try this (you probably have to look at the used path: /opt/jdk1.8.0_06)
[code]-> most of java based application

@rstx: are you sure the nem package is there on the root's package?  Im not sure if you are the root. Do a sudo ls /root to see whats in there and click the keyboard uparrow and go on completing the code . By the way: you can run it even  fron download folder. If you are using the roots ACC, the blockchain / wallet / logs will be stored on the root's folder. Otherwise, i think it'll be at home folder.
Good luck

Android tapatalk =)

His shell prompt says "root@cubieez:~#" so he should be root.

By the way: You shouldn't be looged in as root (unless you really need to).

@rtstrx:
What is it saying when you do "java -version"?
How did you install jdk 8?




Ok, I see.
Well if you are running a gui (Xfce e.g.) then you have to open another terminal and "sh nix.runNcc.sh".
If you are not running a gui then you have to switch to another terminal by CTRL+ALT+F2 (or F3-F7) and do "sh nix.runNcc.sh" from there.

I'm using putty from my windows pc, so i start Nis (until "ready to serve" and open new session.
But now when i run Ncc i see:
[code]...
22:07:45 WARNING Timer TIME SYNCHRONIZATION raised exception: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException
...
[/code]
If i go with mi browser to the port 8989 i see the client interface perfectly but on the top there is "Nis is not available"


Im not so sure if the Devs implemented a feature in which you dont need the correct clock synchronization( if clock have wrong hour and date, it was supposed to not work).

As the little machine are not so powerful, I notice my windows machine ( AMd 7850K APU 4 core @ 4 GHZ) takes, sometimes, 2 or 3 minutes to change the red strip message from 127.0.0.1:8989 to the yellow message.

By the way... the modens Door 7890 are directed to your machiane IP?

As they are making modifications, this could be a clue about whats happening.

:)


Date and time are correct and door 7890 are directed to cubie ip.

I've tried also to download again files, but results are the same:

NIS start successfully and with no warning (ready to serve)
NCC start but with the time sincornization warning (i posted in in the previous post).

If i go with my PC browser to …:8989 the UI appeare perfectly but on the top is see "NIS unavailable"

  :frowning: :frowning:

NXt client is running perfectly on the same machine.


I've tried also to download again files, but results are the same:
NIS start successfully and with no warning (ready to serve)
NCC start but with the time sincornization warning (i posted in in the previous post).
If i go with my PC browser to .....:8989 the UI appeare perfectly but on the top is see "NIS unavailable"

  :( :(
NXt client is running perfectly on the same machine.


How many time did you wait?

If on a very fast processor machine it can take some time, its very possible to take more than 5 minutes so you can be able to start the client on this little machines.


I've tried also to download again files, but results are the same:
NIS start successfully and with no warning (ready to serve)
NCC start but with the time sincornization warning (i posted in in the previous post).
If i go with my PC browser to .....:8989 the UI appeare perfectly but on the top is see "NIS unavailable"

  :( :(
NXt client is running perfectly on the same machine.


How many time did you wait?

If on a very fast processor machine it can take some time, its very possible to take more than 5 minutes so you can be able to start the client on this little machines.

Ok, i'm trying with new 0.4.36 and i'll wait some time before statine ncc.

Thank  for recommending removing root permission, but I leave as is. I like to have administrator mode

Now I have java installed, but only possible for debian (cubieboard 2) is jdk-8u6-linux-arm-vfp-hflt.tar.gz :

http://www.webupd8.org/2014/03/how-to-install-oracle-java-8-in-debian.html

root@cubieez:~# java -version 
java version "1.8.0_06" 
Java™ SE Runtime Environment (build 1.8.0_06-b23) 
Java HotSpot™ Client VM (build 25.6-b23, mixed mode) 
root@cubieez:~# 


When i try to run nis, this error appears:

root@cubieez:~# sh /root/package/nix.runNis.sh 
/root/package/nix.runNis.sh: 3: cd: can't cd to nis 
Error: Could not find or load main class org.nem.core.deploy.CommonStarter 
/root 

Thanks!!!


Thank  for recommending removing root permission, but I leave as is. I like to have administrator mode
Now I have java installed, but only possible for debian (cubieboard 2) is jdk-8u6-linux-arm-vfp-hflt.tar.gz :
http://www.webupd8.org/2014/03/how-to-install-oracle-java-8-in-debian.html
root@cubieez:~# java -version 
java version "1.8.0_06" 
Java(TM) SE Runtime Environment (build 1.8.0_06-b23) 
Java HotSpot(TM) Client VM (build 25.6-b23, mixed mode) 
root@cubieez:~# 
When i try to run nis, this error appears:
root@cubieez:~# sh /root/package/nix.runNis.sh 
/root/package/nix.runNis.sh: 3: cd: can't cd to nis 
Error: Could not find or load main class org.nem.core.deploy.CommonStarter 
/root 

Thanks!!!


Just be aware by using the roots ACC.

if someone can be able to get inside your Pc, with the roots ACC logged on, he will do a lot of chaos.

Thats not a good practice... thats it.

By the way, why you moved the package to roots folder?

Let it on the Download or Documents folder. As you are as logged as root it really doesnt matter where the files are anyway... but If I remember, the system permissions put some restrictions to some actions inside roots folder....

but changing the folder, at least, you'll be able to navigate the folder with mouse or cd command very easil.y

cheers and good luck.