I'm not so sure what is error 306, but to harvest you need 10 k + coins and whith age 24 hours + too.
Maybe this is it.
One Click Install is here - please check the OP.
One-click-install-client.
1. It's ok, all is working, transaction is successful, harvesting on, 0,05%. But if i attempt 'Boot Local Node', i get error 305 or 306 or 601 in different cases.
2. The wallet is in the same place C:/Users/[username]/ncc/*.wlt. Where is the database file *.db now?
One-click-install-client.
1. It's ok, all is working, transaction is successful, harvesting on, 0,05%. But if i attempt 'Boot Local Node', i get error 305 or 306 or 601 in different cases.
2. The wallet is in the same place C:/Users/[username]/ncc/*.wlt. Where is the database file *.db now?
From gimre:
We're aware of 1. It's a result of some last-minute changes, but if you can send transactions it means your node is booted.
2 - c:/users/[username]/nem/nis/data
Most browsers considers applications of java plugin unsafe , these warnings will appear.
There is a way to run it on java Next gen plugin, instead of the old and insecure?
In case of webstart: menu -> close program, starting it again should start new version (0.0.74)
new packages:
1eed42261bc684e4b65c765923adcb32 nis-ncc-0.0.74.tgz
24f8aacae94152ffd043ad62bf5e90b45b62c2ab nis-ncc-0.0.74.tgz
if you're running NIS only, there's no reason to switch, there are mostly fixes on NCC side.
In case of webstart: menu -> close program, starting it again should start new version (0.0.74)
new packages:
1eed42261bc684e4b65c765923adcb32 nis-ncc-0.0.74.tgz
24f8aacae94152ffd043ad62bf5e90b45b62c2ab nis-ncc-0.0.74.tgz
if you're running NIS only, there's no reason to switch, there are mostly fixes on NCC side.
Please update the first post to reflect the 0.7.4 release.
I tested the 0.7.4 deployment today on my Windows 8.1 workstation using Java 8 and Chrome, here is some feedback:
Generally the WebStart client launched correctly, both NIS and NCC were started, but there are few rough edges we need to smooth:
1. Using Chrome, clicking on the "Yes, start NCC for me" link did not launch NEM but instead downloaded the .jnlp file. Chrome then displayed the scary "This file can harm your computer" status message. Once I choose to keep the file and then click it, NEM launched correctly but this is not a good welcome message for new users.
2. After launching the jnlp file both NIS and NCC started and I could verify this in the task manager but then nothing happens… Ideally I would expect webStart to launch a browser session and point it to the NCC or at least tell me to do this myself.
3. Once I launched my wallet by manually opening the browser, it came up saying NIS is disconnected. I realize that it takes time for NIS to load but in my case it took around 10 minutes until the NIS finished its synchronization and during this time the wallet displayed all kinds of funny error messages.
I think the right way to implement this is that the NIS is fully available for NCC connections when launched (10 seconds max) and then while its loading the blockchain it provides the NCC (and the wallet) status updates reported to the user wallet.
4. Then there the issue of booting, it always confuses me whether my wallet is booted or not. If it's already booted and I try to boot it again I'm getting either a 305 or 601 error messages, why can't we just say that the wallet is already booted ? Also I would like to see an indication in the UI that my wallet is booted. Frankly, I don't understand why you cannot boot the wallet automatically upon login. What good is a wallet which is not booted ?
I tested the 0.7.4 deployment today on my Windows 8.1 workstation using Java 8 and Chrome, here is some feedback:
Generally the WebStart client launched correctly, both NIS and NCC were started, but there are few rough edges we need to smooth:
1. Using Chrome, clicking on the "Yes, start NCC for me" link did not launch NEM but instead downloaded the .jnlp file. Chrome then displayed the scary "This file can harm your computer" status message. Once I choose to keep the file and then click it, NEM launched correctly but this is not a good welcome message for new users.
2. After launching the jnlp file both NIS and NCC started and I could verify this in the task manager but then nothing happens... Ideally I would expect webStart to launch a browser session and point it to the NCC or at least tell me to do this myself.
3. Once I launched my wallet by manually opening the browser, it came up saying NIS is disconnected. I realize that it takes time for NIS to load but in my case it took around 10 minutes until the NIS finished its synchronization and during this time the wallet displayed all kinds of funny error messages.
I think the right way to implement this is that the NIS is fully available for NCC connections when launched (10 seconds max) and then while its loading the blockchain it provides the NCC (and the wallet) status updates reported to the user wallet.
4. Then there the issue of booting, it always confuses me whether my wallet is booted or not. If it's already booted and I try to boot it again I'm getting either a 305 or 601 error messages, why can't we just say that the wallet is already booted ? Also I would like to see an indication in the UI that my wallet is booted. Frankly, I don't understand why you cannot boot the wallet automatically upon login. What good is a wallet which is not booted ?
@1: That's a chrome thing. There's a guide on how to circumvent that but I agree that that's not optimal.
@2: Usually the browser is opened automatically. Never heard that it wasn't.
@3: NCC isn't usable until NIS is fully started which shouldn't take longer than about 10 secs durin which NCC shows a message telling people exactly that.
@4: Yes, that's not ideal right now.
Is there any way you could provide a video of that strange behaviour ?
I cleared up the Java Plugin cache and launched NEM again, now it's really using 0.7.4
@1 - Understood
@2 - Ignore, my mistake
@3 - I'm getting "NIS UNAVAILABLE Disconnected from NIS, waiting for connection…" when the browser is opened and many "14:34:56 INFO isConnected is false. Exception received <org.nem.core.connect.FatalPeerException: java.net.ConnectException: Connection refused: no further information> : <java.net.ConnectException: Connection refused: no further information> (org.nem.ncc.connector.b isConnected)" messages in the Java console.
It definitely takes more than 10 seconds but it recovers eventually. Again I think that is very important that NIS opens up the Http socket quickly even before it is fully ready so that it can provide better progress feedback to the NCC.
Would you like me to send some log files ?
@4 - Ok
The following exception is displayed in the NIS log from time to time:
14:23:14 WARNING Timer BROADCAST raised exception: org.nem.core.connect.FatalPeerException: Peer returned unexpected data
java.util.concurrent.CompletionException: org.nem.core.connect.FatalPeerException: Peer returned unexpected data
at java.util.concurrent.CompletableFuture.internalComplete(Unknown Source)
at java.util.concurrent.CompletableFuture$ThenApply.run(Unknown Source)
at java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
at java.util.concurrent.CompletableFuture.complete(Unknown Source)
at org.nem.core.connect.HttpMethodClient$a.completed(HttpMethodClient.java:192)
at org.nem.core.connect.HttpMethodClient$a.completed(HttpMethodClient.java:184)
at org.apache.http.concurrent.BasicFuture.completed(BasicFuture.java:115)
at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:169)
at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:349)
at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady(HttpAsyncRequestExecutor.java:236)
at org.apache.http.impl.nio.client.LoggingAsyncRequestExecutor.inputReady(LoggingAsyncRequestExecutor.java:87)
at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:267)
at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:73)
at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:37)
at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:113)
at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:584)
at java.lang.Thread.run(Unknown Source)
Caused by: org.nem.core.connect.FatalPeerException: Peer returned unexpected data
at org.nem.core.connect.f.a(HttpJsonResponseStrategy.java:28)
at org.nem.core.connect.d.a(HttpDeserializerResponseStrategy.java:32)
at org.nem.core.connect.d.b(HttpDeserializerResponseStrategy.java:14)
at org.nem.core.connect.HttpMethodClient.a(HttpMethodClient.java:120)
at org.nem.core.connect.HttpMethodClient$$Lambda$85/1813341691.apply(Unknown Source)
… 21 more
(org.nem.nis.NisAsyncTimerVisitor b)
It doesn't seem to cause any functional problem.
Can someone look into this transaction:
TRANSACTION DETAILS
ID 7398133269104061000
Hash 66ab7302e1f26c0004c082f5dc59499889cb83babf8d382f7d00e1ff8b322692
Transaction Type Self
Sender TBYGAN-DYNZ6V-5GEFQA-AYD4RD-X6NVSS-AKHDK4-XII7
Recipient TBYGAN-DYNZ6V-5GEFQA-AYD4RD-X6NVSS-AKHDK4-XII7
Message To myself
Timestamp Jul 19, 2014 00:13:39
Confirmations 4137
Amount 100.00 NEM
Fee 2.00 NEM
I sent it to myself on July 19th but it still shows in status pending in wallet. Is it just a display problem ?
It looks like there's a problem with the search function of the block explorer http://chain.nem.ninja/ try searching for transaction 4537308242019759000 getting a message box displaying "500" and later "Server Internal Error".
Folks, are there public client (or server) APIs I can use to monitor things like transaction status, transactions in a block etc …
It looks like there's a problem with the search function of the block explorer http://chain.nem.ninja/ try searching for transaction 4537308242019759000 getting a message box displaying "500" and later "Server Internal Error".
That's because 4537308242019759000 isn't a valid hash to search for. What is that ?
About the rest...I think the folks are actually working on fixing that issue. I'm not quite sure it's that issue you are having though but I'm sure one of the core devs will look at it soon enough.
The following exception is displayed in the NIS log from time to time:
14:23:14 WARNING Timer BROADCAST raised exception: org.nem.core.connect.FatalPeerException: Peer returned unexpected data
java.util.concurrent.CompletionException: org.nem.core.connect.FatalPeerException: Peer returned unexpected data
...
It doesn't seem to cause any functional problem.
You can safely ignore that message. Broadcast will try to send data to all nodes that are considered active but sometimes a node went offline. "returned unexpected data" usually means an empty string was returned, nothing to worry about.
@3 - I'm getting "NIS UNAVAILABLE Disconnected from NIS, waiting for connection..." when the browser is opened and many "14:34:56 INFO isConnected is false. Exception received <org.nem.core.connect.FatalPeerException: java.net.ConnectException: Connection refused: no further information> : <java.net.ConnectException: Connection refused: no further information> (org.nem.ncc.connector.b isConnected)" messages in the Java console.
It definitely takes more than 10 seconds but it recovers eventually. Again I think that is very important that NIS opens up the Http socket quickly even before it is fully ready so that it can provide better progress feedback to the NCC.
That problem will hopefully be solved with the next version.
It looks like there's a problem with the search function of the block explorer http://chain.nem.ninja/ try searching for transaction 4537308242019759000 getting a message box displaying "500" and later "Server Internal Error".
That's because 4537308242019759000 isn't a valid hash to search for. What is that ?
About the rest...I think the folks are actually working on fixing that issue. I'm not quite sure it's that issue you are having though but I'm sure one of the core devs will look at it soon enough.
This is the transaction I'm looking for:
TRANSACTION DETAILS
ID 4537308242019759000
Hash 3ef7c1ce720a34db54a59c8edfe025e223917e25d2713c7e662ed223ac845e04
Transaction Type Outgoing
Sender TBYGAN-DYNZ6V-5GEFQA-AYD4RD-X6NVSS-AKHDK4-XII7
Recipient TCCHZF-PYOVI3-VSVQEQ-KSW6YV-P6WUET-CNTQ77-ZSOX
Message 1
Timestamp Jul 02, 2014 11:45:09
Confirmations 23666
Amount 60 000.00 NEM
Fee 6.00 NEM
Searching for transaction id 4537308242019759000 returns 500 error.
Searching for account id TBYGAN-DYNZ6V-5GEFQA-AYD4RD-X6NVSS-AKHDK4-XII7 returns "Invalid search entry!"
Searching for the transaction hash 3ef7c1ce720a34db54a59c8edfe025e223917e25d2713c7e662ed223ac845e04 does bring up the transaction information.
I'd like to also point out the following usability problems:
1. The search button does not work, you need to press <Enter> while the focus is on the "Search" field in order to submit.
2. The search input field is too short.
3. The "Transaction Info" frame is closed when you click it. This makes it difficult to copy/paste information from this window. It makes more sense to close it only when click the Red X.
(Using Chrome for all tests but it seems to work the same with IE)
I'd like to also point out the following usability problems:
1. The search button does not work, you need to press <Enter> while the focus is on the "Search" field in order to submit.
2. The search input field is too short.
3. The "Transaction Info" frame is closed when you click it. This makes it difficult to copy/paste information from this window. It makes more sense to close it only when click the Red X.
(Using Chrome for all tests but it seems to work the same with IE)
Thx for the feedback. I will forward it to the block explorer coder.
It looks like there's a problem with the search function of the block explorer http://chain.nem.ninja/ try searching for transaction 4537308242019759000 getting a message box displaying "500" and later "Server Internal Error".
That's because 4537308242019759000 isn't a valid hash to search for. What is that ?
About the rest...I think the folks are actually working on fixing that issue. I'm not quite sure it's that issue you are having though but I'm sure one of the core devs will look at it soon enough.
This is the transaction I'm looking for:
TRANSACTION DETAILS
ID 4537308242019759000
Hash 3ef7c1ce720a34db54a59c8edfe025e223917e25d2713c7e662ed223ac845e04
Transaction Type Outgoing
Sender TBYGAN-DYNZ6V-5GEFQA-AYD4RD-X6NVSS-AKHDK4-XII7
Recipient TCCHZF-PYOVI3-VSVQEQ-KSW6YV-P6WUET-CNTQ77-ZSOX
Message 1
Timestamp Jul 02, 2014 11:45:09
Confirmations 23666
Amount 60 000.00 NEM
Fee 6.00 NEM
Searching for transaction id 4537308242019759000 returns 500 error.
Searching for account id TBYGAN-DYNZ6V-5GEFQA-AYD4RD-X6NVSS-AKHDK4-XII7 returns "Invalid search entry!"
Searching for the transaction hash 3ef7c1ce720a34db54a59c8edfe025e223917e25d2713c7e662ed223ac845e04 does bring up the transaction information.
I'd like to also point out the following usability problems:
1. The search button does not work, you need to press <Enter> while the focus is on the "Search" field in order to submit.
2. The search input field is too short.
3. The "Transaction Info" frame is closed when you click it. This makes it difficult to copy/paste information from this window. It makes more sense to close it only when click the Red X.
(Using Chrome for all tests but it seems to work the same with IE)
The search currently only works with hashes but of course that'll be changed in the future.
Usability hasn't been given too much attention because after the branding is done a full redesign will take place anyway but we'll consider your points then :)