I am having problems with Avast too. Here are the errors. The main problem is that I am stuck at block 5872
Infection details are URL: http://108.61.203.140:7980/node/info
Infection: Mal
Process: C:\ProgramFiles(x86)\Java\jre1.8.0_31\bin\jp2launcher.exe
(I've accidentally edit your post, sorry for that 
- gimre)
I am having problems with Avast too. Here are the errors. The main problem is that I am stuck at block 5872
Infection details are URL: http://108.61.203.140:7980/node/info
Infection: Mal
Process: C:\ProgramFiles(x86)\Java\jre1.8.0_31\bin\jp2launcher.exe
http://s25.postimg.org/qby2qyhxr/photo_2015_02_10_01_57_49.jpg
Lol, clearly some kind of FP, in Avast's firewall.
Is there any way to get some more detailed info in avast WHY did it actually detect a threat?
This is found in Jeffs NIS log repeatedly with different nodes:2015-02-10 01:32:03.275 INFO entering /push/block [199.217.112.135] (org.nem.nis.controller.interceptors.AuditInterceptor preHandle)<br />2015-02-10 01:32:03.484 INFO received: 1 from Hi, I am Alice4 <TALICE4AQNH5TE7O43RZ5FPJ3AC6HCFTSOO7B3GF> (signer: TCCBMXVNXDEEPMS5W3MYH7RCR7JLIRP53Q7UR2N7) (org.nem.nis.service.PushService a)<br />2015-02-10 01:32:03.484 INFO block height: 11509 (org.nem.nis.service.PushService t)<br />2015-02-10 01:32:03.484 INFO isLastBlockParent result: false (org.nem.nis.BlockChain f)<br />2015-02-10 01:32:03.484 INFO last block height: 5872 (org.nem.nis.BlockChain f)<br />2015-02-10 01:32:03.485 INFO Warning: ValidationResult=FAILURE_ENTITY_UNUSABLE_OUT_OF_SYNC (org.nem.nis.service.PushService a)<br />2015-02-10 01:32:03.485 INFO exiting /push/block [199.217.112.135] (org.nem.nis.controller.interceptors.AuditInterceptor afterCompletion)
And this:2015-02-10 01:32:42.040 WARNING Timer SYNC raised exception: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException<br />java.util.concurrent.CompletionException: org.nem.core.connect.BusyPeerException: 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$HttpMethodClientFutureCallback.failed(HttpMethodClient.java:199)<br /> at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:130)<br /> at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.failed(DefaultClientExchangeHandlerImpl.java:258)<br /> at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.timeout(HttpAsyncRequestExecutor.java:289)<br /> at org.apache.http.impl.nio.client.LoggingAsyncRequestExecutor.timeout(LoggingAsyncRequestExecutor.java:120)<br /> at org.apache.http.impl.nio.client.InternalIODispatch.onTimeout(InternalIODispatch.java:84)<br /> at org.apache.http.impl.nio.client.InternalIODispatch.onTimeout(InternalIODispatch.java:37)<br /> at org.apache.http.impl.nio.reactor.AbstractIODispatch.timeout(AbstractIODispatch.java:172)<br /> at org.apache.http.impl.nio.reactor.BaseIOReactor.sessionTimedOut(BaseIOReactor.java:255)<br /> at org.apache.http.impl.nio.reactor.AbstractIOReactor.timeoutCheck(AbstractIOReactor.java:491)<br /> at org.apache.http.impl.nio.reactor.BaseIOReactor.validate(BaseIOReactor.java:205)<br /> at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:281)<br /> at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)<br /> at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:586)<br /> at java.lang.Thread.run(Unknown Source)<br />Caused by: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException<br /> at org.nem.core.connect.HttpMethodClient$HttpMethodClientFutureCallback.b(HttpMethodClient.java:204)<br /> ... 15 more<br />Caused by: java.net.SocketTimeoutException<br /> ... 12 more<br /> (org.nem.core.async.NemAsyncTimerVisitor b)
This is found in Jeffs NIS log repeatedly with different nodes:
[code]2015-02-10 01:32:03.275 INFO entering /push/block [199.217.112.135] (org.nem.nis.controller.interceptors.AuditInterceptor preHandle)
2015-02-10 01:32:03.484 INFO received: 1 from Hi, I am Alice4 <TALICE4AQNH5TE7O43RZ5FPJ3AC6HCFTSOO7B3GF> (signer: TCCBMXVNXDEEPMS5W3MYH7RCR7JLIRP53Q7UR2N7) (org.nem.nis.service.PushService a)
2015-02-10 01:32:03.484 INFO block height: 11509 (org.nem.nis.service.PushService t)
2015-02-10 01:32:03.484 INFO isLastBlockParent result: false (org.nem.nis.BlockChain f)
2015-02-10 01:32:03.484 INFO last block height: 5872 (org.nem.nis.BlockChain f)
2015-02-10 01:32:03.485 INFO Warning: ValidationResult=FAILURE_ENTITY_UNUSABLE_OUT_OF_SYNC (org.nem.nis.service.PushService a)
2015-02-10 01:32:03.485 INFO exiting /push/block [199.217.112.135] (org.nem.nis.controller.interceptors.AuditInterceptor afterCompletion)[/code]
And this:
[code]2015-02-10 01:32:42.040 WARNING Timer SYNC raised exception: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException
java.util.concurrent.CompletionException: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException
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.completeExceptionally(Unknown Source)
at org.nem.core.connect.HttpMethodClient$HttpMethodClientFutureCallback.failed(HttpMethodClient.java:199)
at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:130)
at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.failed(DefaultClientExchangeHandlerImpl.java:258)
at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.timeout(HttpAsyncRequestExecutor.java:289)
at org.apache.http.impl.nio.client.LoggingAsyncRequestExecutor.timeout(LoggingAsyncRequestExecutor.java:120)
at org.apache.http.impl.nio.client.InternalIODispatch.onTimeout(InternalIODispatch.java:84)
at org.apache.http.impl.nio.client.InternalIODispatch.onTimeout(InternalIODispatch.java:37)
at org.apache.http.impl.nio.reactor.AbstractIODispatch.timeout(AbstractIODispatch.java:172)
at org.apache.http.impl.nio.reactor.BaseIOReactor.sessionTimedOut(BaseIOReactor.java:255)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.timeoutCheck(AbstractIOReactor.java:491)
at org.apache.http.impl.nio.reactor.BaseIOReactor.validate(BaseIOReactor.java:205)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:281)
at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:586)
at java.lang.Thread.run(Unknown Source)
Caused by: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException
at org.nem.core.connect.HttpMethodClient$HttpMethodClientFutureCallback.b(HttpMethodClient.java:204)
... 15 more
Caused by: java.net.SocketTimeoutException
... 12 more
(org.nem.core.async.NemAsyncTimerVisitor b)[/code]
The first log part means Jeff is not synced (are you on a fork, Jeff? if so, delete db and restart. You can give the NIS logs to me too if you want)
The second log part can be ignored, the node simply tried to get time information from a node that is busy (that happens frequently).
We've added delayed loading, in ui it looks as follows. So nis tries to start as fast as possible. And then it loads blocks.
First I thought: Hell yeah! Now I can fire up NIS and NCC on the cubie, log into the wallet and leave.
But no, its not possible to log in until the block analysis (in the GUI its called "Loading blocks from db, at block: xyz") is done:
"ERROR 602
Cannot perform any operations until db is fully loaded."
Isn't it possible to log in while the analysis is going on and maybe even start harvesting in the GUI (it will in fact start after analysis is done), but for a cubie node this would be so much better!
It's first version of delayed loading, so forgive us the hiccups.
There are two possible solutions:
a) we can introduce additional config variable, that will cause nis to start "the old way"
b) you can create bit better auto-start-harvesting script, here's how
[code]
$ curl http://localhost:7890/status
{"code":6,"type":4,"message":"status"}
[/code]
Type:4 means it's a "STATUS" result, now regarding code:
[code]
0: Unknown status.
1: NIS is stopped.
2: NIS is starting.
3: NIS is running.
4: NIS is booting the local node (implies NIS is running).
5: The local node is booted (implies NIS is running).
6: The local node is synchronized (implies NIS is running and the local node is booted).
7: No other nodes visible (implies NIS is running and the local node is booted, but probably disconnected from internet).
8: Loading the db.
[/code]
So basically until you get status:6 in response it doesn't make much sense to start harvesting
I am having problems with Avast too. Here are the errors. The main problem is that I am stuck at block 5872
Infection details are URL: http://108.61.203.140:7980/node/info
Infection: Mal
Process: C:\ProgramFiles(x86)\Java\jre1.8.0_31\bin\jp2launcher.exe
http://s25.postimg.org/qby2qyhxr/photo_2015_02_10_01_57_49.jpg
Lol, clearly some kind of FP, in Avast's firewall.
Is there any way to get some more detailed info in avast WHY did it actually detect a threat?
I went through the settings and couldn't find anyway to get any more information. Right now I have Avast on "silent gaming mode" and no more pop-ups.
Nembit and I are both having problems though. We both got stuck at blocks 5670. And we have both deleted the chains and downloaded again and we are both still getting stuck. Not sure why.
Here are my log files. https://www.dropbox.com/s/pmosayjinju5fmc/logs.zip?dl=0
oh one last bit of information. I am guessing I am on a fork. At one point when I was downloading the chain, it stopped around the 4000 block and NIS went green and said I was synced (clearly I wasn't). Then after 30 seconds went yellow again and started adding new blocks.
It's really fast. I had problems for an account which was a cosignatory for two different accounts. I couldn't send XEM using this account in 0.5.4. But now it's lightning fast. Also love the part where just typing the account label gives the address.
But the parts per mille is a bit confusing.
On the dashboard it shows 6.xx 0/00 but clicking upon transaction details, it shows the importance around 0.6%?
Also what s the difference between vested and normal balances?
On a sidenote, I harvested the following blocks:
Block #11495 Feb 09, 2015 21:48:53 376 847.21
Block #11491 Feb 09, 2015 21:47:10 355 954.99
Block #11464 Feb 09, 2015 21:24:46 386 207.46
Block #11444 Feb 09, 2015 20:55:49 114 900.56.
Crazy transaction fees ;D
as I've mentioned somewhere here, we wanted to switch to per mille, but right now it's only on main screen I think, in final version, we might switch to 'base point'
ok…I got stuck on block 5670…same as Jeff…for ages…have now broken out to block number 5799…again, just like Jeff…is this similar to blockchain bloat …?
ok.........I got stuck on block 5670...same as Jeff....for ages......have now broken out to block number 5799.......again, just like Jeff..........is this similar to blockchain bloat ...?
we're trying to go through jeff's log to see if there is anything wrong
We've identified an issue, by hardening some checks, we've introduced forking change.
For now the only fix is getting db from bob: http://bob.nem.ninja/
it's the file named http://bob.nem.ninja/nis5.h2.db-11772.tgz
(there's also gpg sig for it, if you need one)
No remote NIS found in the network, disconnected from internet?
I am getting this message at the top in an orange bar. I had already succesfully imported the 50m private key from gimre, so I know that I was connected for a few seconds. I have a POI showing up but this message is constant. Thanks
I deleted the old database file and put in the new one I downloaded. Upon starting NEM I got an error that said something similar to, "oops, we can't perform any operations until the database is fully synced." Error 602 That makes sense.
The the NEM client didn't autoboot so I had to set it to do that.
I started doing some transactions and it wouldn't work. Everything was pending. Then I looked at the block explorer. All the blocks were full for more than an hour. It took my transaction 22 blocks to clear. That means around 2600 transactions in que ahead of me! Wow. hahaha. But eventually it all worked well. 
Okay, I have done a lot of testing both on Windows and Mac. Generally NEM just keeps on getting better and better. :-) It is very clear a lot of hard work is going into this.
Here are things I noticed that might be considered issues.
1. When using the Mac app, when I tried to label my primary account via clicking the gear icon, I was given an error message saying that account didn
When trying to convert MS, the temp memory is full with
any fee…
We've identified an issue, by hardening some checks, we've introduced forking change.
For now the only fix is getting db from bob: http://bob.nem.ninja/
...
Getting db from bob doesn't help. In this case NIS gets stuck at block 9216
'Loading blocks from db, at block: 9216'
We've identified an issue, by hardening some checks, we've introduced forking change.
For now the only fix is getting db from bob: http://bob.nem.ninja/
...
Getting db from bob doesn't help. In this case NIS gets stuck at block 9216
'Loading blocks from db, at block: 9216'
I had the same issue until I cleaned out the old version.
Shutdown NEM.
Run: "javaws -viewer" and delete Trace/Log Files and Cached Applications/Applets.
Delete the C:\Users\<username>\nem\nis\data directory.
Unzip nis5.h2.db-11772.tgz and put the nis5.h2 file in the "C:\Users\<username>\nem\nis\data" folder.
After doing that, NEM 0.5.5-BETA loaded and synced fast.
If you still have issues you might try the more thorough removal:
https://forum.ournem.com/beta-launch-discussion/nem-beta-0-4-17/msg8834/#msg8834
everything was working fine for me, but then i tried to enter address book and the "address book" button on the left was just acting like a dead button… i mean i would click it, and nothing would change(stay on dashboard). transactions and all other functions harvested blocks, settings cog etc all work though… im rebooting ncc and connecting to a different node to see if that fixes it.
eidt: working again after a NCC reboot. same node.
We've identified an issue, by hardening some checks, we've introduced forking change.
For now the only fix is getting db from bob: http://bob.nem.ninja/
...
Getting db from bob doesn't help. In this case NIS gets stuck at block 9216
'Loading blocks from db, at block: 9216'
I had the same issue until I cleaned out the old version.
Shutdown NEM.
Run: "javaws -viewer" and delete Trace/Log Files and Cached Applications/Applets.
Delete the C:\Users\<username>\nem\nis\data directory.
Unzip nis5.h2.db-11772.tgz and put the nis5.h2 file in the "C:\Users\<username>\nem\nis\data" folder.
...
Didn't help. Get stuck at block 9216.