Wirralnick, can supply the logs located in c:\users\<user name>\nem\ncc\logs and c:\users\<user name>\nem\nis\logs ?
The logs are huge...?
The logs are huge...?
@warralnick: you can zip the logs before uploading to a file server. Also, you could first delete all logs, then start the nem software and when it doesn't work after 5 mins, shut the software down. The logs shouldn't be that big then.
Round 1 (Windows)
8:10 backed up wallet
8:11 deleted Java programs and NEM folder
8:12 clicked bob.ninja
8:13 opening page came up (really fast. By faster than before and I didn't have to select chrome or any other things. Just clicked on bob.ninja got a file to click on and that was it. Much better than before)
8:15 NIS and NCC is running.
No wallets found.
8:16 pasted in old wallet
8:17 clicked refresh. Old wallet found. Lastpass remembers my old password. I'm in.
8:18 no coins. Staring at client. Remembered I need to boot local mode after seeing message at top.
8:19 message on bottom right says "NIS is running (booted), NIC is running" but message at the top off the screen says "NIS info is not available yet. Trying to retrieve NIS info…"
8:25 closed NOM and wallet. Restarting NOM and client but not Windows.
8:28 I'm back in. I go to settings and click "auto boot" and "save". Then clicked the menu near my name. Clicked to boot node.
8:29 Same messages as before.
"NIS is running (booted), NIC is running" buy message at the top off the screen says "NIS info is not available yet. Trying to retrieve NIS info…"
Still at "unknown block"
Round 2 (Windows)
8:40 turned off windows simulation. Turned off Ubuntu and then restarted them both.
8:41 clicked on the NOM icon on my desktop.
8:43 NOM started up, landing page opened in Chrome. This is great, just one click!
8:45 After waiting a bit NIS is now booted. Open wallet and found all my coins plus some that have been sent since the last time I logged on. Autoboot worked this time because I didn't have to boot in local node.
8:50 still see the same error that I saw last time saying
"NIS is running (booted), NIC is running" buy message at the top off the screen says "NIS info is not available yet. Trying to retrieve NIS info…"
8:51 I try to send a transaction. It works and I get a confirmation. Nice new confirmation message pop-up. Looks good.
9:50 it still says
@jobo: great and detailed description!
"NIS is running (booted), NIC is running" buy message at the top off the screen says "NIS info is not available yet. Trying to retrieve NIS info…"
is a known issue in 0.3.2. If you're able to send transactions (like in round2), it means everything is fine. Can't help with mac, maybe J will be able to.
@jobo: great and detailed description!
"NIS is running (booted), NIC is running" buy message at the top off the screen says "NIS info is not available yet. Trying to retrieve NIS info..."
is a known issue in 0.3.2. If you're able to send transactions (like in round2), it means everything is fine. Can't help with mac, maybe J will be able to.
I only need it to work on one machine, but it would be nice if I had it going on all three. Hahaha.
As a further update. The windows client still has the same message and still says, "at block unknown" next to my account balance, buuuuuut I recently harvested a block in addition to sending out a lot more transactions so I know it is working.
All around except for the message stating "NIS info is not available yet. Trying to retrieve NIS info…" which was already discussed and not a big deal, this version of NEM has been working really well for me. (on Windows) It seems to have loaded easier and faster. It is a bit snappier when operating too. If I left it running before for long periods of time my computer would lag and would need a restart. It now seems unaffected.
I had one problem that I thought was weird. Once and only once upon starting it kept on telling me I didn't have enough funds in my account when trying to send NEM despite having a couple of million sent to me by many people and those coins having lots of confirmations. The time before that incident, I did run my balance down to 0 so I am not sure if that affected it. I turned off windows and started windows and NEM again and was able to send coins right away no problem.
@jabo38s: I will take a look at the logs later.
The message "NIS info is not available yet. Trying to retrieve NIS info…" means that port 7890 is not open for incoming requests in your firewall/router. We already fixed our code to make it more tolerant to closed port issues.
I'm confused how I should be using the remote functionality of NCC. I would like to run NIS on a Raspberry PI so I can keep it serving the NEM network 24x7. I would then like to use NCC on my Windows laptop. I have changed settings on NCC to use remote node and entered the static IP address assigned to the device. I can then logon to NCC. But NIS in the Pi isn't booted and when I then boot the node from in NCC it appears to error because NIS isn't running locally.
KC
I think you need to boot it locally first before you can use it remotely (not 100% sure though).
There are certain calls in the API that are only available locally for security reasons and I'm pretty sure booting is one of them.
I think you need to boot it locally first before you can use it remotely (not 100% sure though).
There are certain calls in the API that are only available locally for security reasons and I'm pretty sure booting is one of them.
Thanks, I'm still not sure it is working as intended. The client and I seemed to be confused as to what is being done locally and what is remote.
Here are my steps:
[li]Start NIS on the remote computer (Raspberry Pi)[/li]
[li]Start NCC on the remote computer (Raspberry Pi)[/li]
[li]Browse to NCC url (http://192.168.10.52:8989/ncc/web/dashboard.html) on remote computer from laptop
(Windows)[/li]
[li]Open wallet presented (wallets are those on the Raspberry Pi) from the laptop browser (Windows)[/li]
[li]Boot node through NCC (Windows)[/li]
[li]Start NEM Monitor on the laptop (Windows) this start NIS, NCC and browser session on the laptop (Windows)[/li]
This is where it starts getting confusing and multiple permutations exist:
[li]I stopped NIS on the laptop, left NCC running, opened NCC in the browser pointing locally and changed settings to look remote host (192.168.10.52)[/li]
[li]Opened a wallet on my laptop[/li]
So now I assume that NCC is running locally on the laptop and pointing to a remote NIS on the Raspberry Pi?
I go to check the client info on the NCC running on the laptop with NIS remote and after a few seconds get an error message (attached)
KC
I think you need to boot it locally first before you can use it remotely (not 100% sure though).
There are certain calls in the API that are only available locally for security reasons and I'm pretty sure booting is one of them.
Thanks, I'm still not sure it is working as intended. The client and I seemed to be confused as to what is being done locally and what is remote.
Here are my steps:
[li]Start NIS on the remote computer (Raspberry Pi)[/li]
[li]Start NCC on the remote computer (Raspberry Pi)[/li]
[li]Browse to NCC url (http://192.168.10.52:8989/ncc/web/dashboard.html) on remote computer from laptop
(Windows)[/li]
[li]Open wallet presented (wallets are those on the Raspberry Pi) from the laptop browser (Windows)[/li]
[li]Boot node through NCC (Windows)[/li]
[li]Start NEM Monitor on the laptop (Windows) this start NIS, NCC and browser session on the laptop (Windows)[/li]
This is where it starts getting confusing and multiple permutations exist:
[li]I stopped NIS on the laptop, left NCC running, opened NCC in the browser pointing locally and changed settings to look remote host (192.168.10.52)[/li]
[li]Opened a wallet on my laptop[/li]
So now I assume that NCC is running locally on the laptop and pointing to a remote NIS on the Raspberry Pi?
I go to check the client info on the NCC running on the laptop with NIS remote and after a few seconds get an error message (attached)
KC
Your steps seem fine so it should ahve worked.
As for the error - please post logs fromt when that happend.
Looks like it is the time sicronization:<br />out 05, 2014 11:22:21 AM org.nem.core.async.NemAsyncTimerVisitor b<br />Timer CHECKING CHAIN SYNCHRONIZATION raised exception: org.nem.core.connect.InactivePeerException: java.net.SocketTimeoutException<br />java.util.concurrent.CompletionException: org.nem.core.connect.InactivePeerException: java.net.SocketTimeoutException<br /> at java.util.concurrent.CompletableFuture.internalComplete(Unknown Source)<br /> at java.util.concurrent.CompletableFuture$ThenApply.run(Unknown Source)<br /> at java.util.concurrent.CompletableFuture.postComplete(Unknown Source)<br /> at java.util.concurrent.CompletableFuture.completeExceptionally(Unknown Source)<br /> at org.nem.core.connect.HttpMethodClient$a.failed(HttpMethodClient.java:202)<br /> at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:130)<br /> at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.connectionRequestFailed(DefaultClientExchangeHandlerImpl.java:308)<br /> at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.access$100(DefaultClientExchangeHandlerImpl.java:63)<br /> at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl$1.failed(DefaultClientExchangeHandlerImpl.java:351)<br /> at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:130)<br /> at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager$InternalPoolEntryCallback.failed(PoolingNHttpClientConnectionManager.java:471)<br /> at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:130)<br /> at org.apache.http.nio.pool.RouteSpecificPool.timeout(RouteSpecificPool.java:166)<br /> at org.apache.http.nio.pool.AbstractNIOConnPool.requestTimeout(AbstractNIOConnPool.java:546)<br /> at org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.timeout(AbstractNIOConnPool.java:750)<br /> at org.apache.http.impl.nio.reactor.SessionRequestImpl.timeout(SessionRequestImpl.java:177)<br /> at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processTimeouts(DefaultConnectingIOReactor.java:213)<br /> at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:157)<br /> at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348)<br /> at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:189)<br /> at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.doExecute(CloseableHttpAsyncClientBase.java:67)<br /> at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.access$000(CloseableHttpAsyncClientBase.java:38)<br /> at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:57)<br /> at java.lang.Thread.run(Unknown Source)<br />Caused by: org.nem.core.connect.InactivePeerException: java.net.SocketTimeoutException<br /> at org.nem.core.connect.HttpMethodClient$a.failed(HttpMethodClient.java:199)<br /> ... 19 more<br />Caused by: java.net.SocketTimeoutException<br /> ... 12 more<br />
Looks like it is the time sicronization:
it's not time synch, it's just sync, and the other side did not respond, nothing to worry about.
Looks like it is the time sicronization:
it's not time synch, it's just sync, and the other side did not respond, nothing to worry about.
but like this I cant receive coins or send them on rasPi
and the system do not syncronize.
do we already have the Makoto's solution to network sincyng? (the one that dont use the localTime to sinchronize)
;)
Here are my steps:
Hi, try this:
[li]start NIS on Raspi (let's say 192.168.0.123) [/li]
[li]start NIS and NCC on laptop[/li]
[li]create wallet on laptop, and open it[/li]
[li]go into settings, change host to Raspi (http://192.168.0.123:7890)[/li]
[li]you can now turn off NIS on laptop[/li]
Share if this helped or not.
@jobo: great and detailed description!
"NIS is running (booted), NIC is running" buy message at the top off the screen says "NIS info is not available yet. Trying to retrieve NIS info..."
is a known issue in 0.3.2. If you're able to send transactions (like in round2), it means everything is fine. Can't help with mac, maybe J will be able to.
I only need it to work on one machine, but it would be nice if I had it going on all three. Hahaha.
As a further update. The windows client still has the same message and still says, "at block unknown" next to my account balance, buuuuuut I recently harvested a block in addition to sending out a lot more transactions so I know it is working.
I don't know if I've harvested a block, but this is what is happening for me when I can get past the lack of booting, which seems to work sometimes if I leave it for ages and keep refreshing the page...
When we upgrade the client to verify downloaded files can be [url=https://forum.ournem.com/index.php?topic=2230.msg4058#msg4058]by PGP public key. It's safe, but it is not convenient. Is it possible to add the SHA-256 code at http://bob.nem.ninja/ for verification, additionally?
Just installed a windows 7 virtual machine. I installed NEM on it with one click and no problems! (After installing java 8)
@jobo: great and detailed description!
"NIS is running (booted), NIC is running" buy message at the top off the screen says "NIS info is not available yet. Trying to retrieve NIS info..."
is a known issue in 0.3.2. If you're able to send transactions (like in round2), it means everything is fine. Can't help with mac, maybe J will be able to.
I only need it to work on one machine, but it would be nice if I had it going on all three. Hahaha.
As a further update. The windows client still has the same message and still says, "at block unknown" next to my account balance, buuuuuut I recently harvested a block in addition to sending out a lot more transactions so I know it is working.
I don't know if I've harvested a block, but this is what is happening for me when I can get past the lack of booting, which seems to work sometimes if I leave it for ages and keep refreshing the page...
I found it helpful to remove old NEM leftovers. I deleted the NEM folder and killed the java. Here is more troubleshooting info. https://forum.ournem.com/index.php?topic=2471.msg5828#msg5828
Here are my steps:
Hi, try this:
[li]start NIS on Raspi (let's say 192.168.0.123) [/li]
[li]start NIS and NCC on laptop[/li]
[li]create wallet on laptop, and open it[/li]
[li]go into settings, change host to Raspi (http://192.168.0.123:7890)[/li]
[li]you can now turn off NIS on laptop[/li]
Share if this helped or not.
Hi Gimer,
I tried your suggestion but ended up with an Unknown error message when trying to boot the node. Attached is a screenshot of the RaspberryPI real-time logging at the boot I attempt to boot the local node on in NCC which was configured to use remote host (192.168.10.52).
KC