Well then wait till its synchronized and check again after that 
after my internet goes down, several transactions were unconfirmed, but after he returned half an hour later, the blockchain processed 120 transactions per block, but my transactions have not been confirmed so far, an hour ago … …
They are in the queue or will never confirm?
Should I report this as an issue? The ehancement possible?
Icharles123, it depends on the situation. If the network was under pressure (every block has 120 transactions), then the fees decide if your transactions get placed into a block. Do you know how high your fees were compared to the fees that the spam bots used?
Ok, i put the minimun fee. So my transactions were slow to confirm. But the important thing is that they are confirmed, what happened. :)
Icharles123, it depends on the situation. If the network was under pressure (every block has 120 transactions), then the fees decide if your transactions get placed into a block. Do you know how high your fees were compared to the fees that the spam bots used?
Even so, the network produced empty blocks or less than 120 TXs, although my transactions are waiting.
Hello.
I have to report a strange behaviour.
I use latest standalone version on linux.
I start NIS from command line.
Wait until it writes is ready to serve on 127.0.0.1:7890
Then i start NCC from command line.
Wait until it writes is ready on 127.0.0.1:8989
Then I login into my wallet and wait until is synchronizes.
While synchronization is running for 15 or 20 minutes then suddenly NCC outputs the following error below into the console.
After that NCC can not connect to NIS any more unless restart NIS process and NCC again.
This does not happen every time but very often it does.<br />19:50:52 INFO entering /ncc/api/account/transactions/all [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor preHandle)<br />19:50:52 INFO entering /ncc/api/wallet/account/remote/status [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor preHandle)<br />19:50:53 INFO exiting /ncc/api//info/nis/chain/height [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor afterCompletion)<br />19:50:54 INFO entering /ncc/api//info/nis/chain/height [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor preHandle)<br />19:51:01 INFO exiting /ncc/api//info/nis/chain/height [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor afterCompletion)<br />19:51:01 INFO entering /ncc/api//info/nis/chain/height [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor preHandle)<br />19:51:02 SEVERE Http Status Code 500: java.net.SocketTimeoutException (org.nem.core.connect.ErrorResponse <init>)<br />19:51:02 INFO exiting /ncc/api/info/nis [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor afterCompletion)<br />19:51:03 SEVERE Http Status Code 500: java.net.SocketTimeoutException (org.nem.core.connect.ErrorResponse <init>)<br />19:51:03 INFO exiting /ncc/api/wallet/account/remote/status [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor afterCompletion)<br />19:51:10 INFO exiting /ncc/api//info/nis/chain/height [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor afterCompletion)<br />19:51:10 INFO entering /ncc/api//info/nis/chain/height [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor preHandle)<br />19:51:10 INFO exiting /ncc/api//info/nis/chain/height [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor afterCompletion)<br />19:51:10 INFO entering /ncc/api//info/nis/chain/height [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor preHandle)<br />19:51:11 SEVERE Http Status Code 500: java.net.SocketTimeoutException (org.nem.core.connect.ErrorResponse <init>)<br />19:51:11 INFO exiting /ncc/api/account/transactions/all [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor afterCompletion)<br />19:51:11 SEVERE Http Status Code 500: java.net.SocketTimeoutException (org.nem.core.connect.ErrorResponse <init>)<br />19:51:11 INFO exiting /ncc/api/account/transactions/all [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor afterCompletion)<br />19:51:11 SEVERE Http Status Code 500: java.net.SocketTimeoutException (org.nem.core.connect.ErrorResponse <init>)<br />19:51:18 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 /> at java.util.concurrent.CompletableFuture.internalComplete(CompletableFuture.java:205)<br /> at java.util.concurrent.CompletableFuture$ThenApply.run(CompletableFuture.java:723)<br /> at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:193)<br /> at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2361)<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:279)<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:584)<br /> at java.lang.Thread.run(Thread.java:745)<br />Caused by: org.nem.core.connect.BusyPeerException: java.net.SocketTimeoutException<br /> at org.nem.core.connect.HttpMethodClient$HttpMethodClientFutureCallback.wrapException(HttpMethodClient.java:204)<br /> ... 15 more<br />Caused by: java.net.SocketTimeoutException<br /> ... 12 more<br /> (org.nem.core.async.NemAsyncTimerVisitor notifyOperationCompleteExceptionally)<br />19:51:20 SEVERE Http Status Code 500: java.net.SocketTimeoutException (org.nem.core.connect.ErrorResponse <init>)<br />19:51:20 INFO exiting /ncc/api//info/nis/chain/height [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor afterCompletion)<br />19:51:20 INFO entering /ncc/api//info/nis/chain/height [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor preHandle)<br />19:51:21 SEVERE Http Status Code 500: java.net.SocketTimeoutException (org.nem.core.connect.ErrorResponse <init>)<br />19:51:22 INFO entering /ncc/api/account/transactions/all [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor preHandle)<br />
I sometimes see that on the cubietruck but its no crash. After some time (usually seconds) its all good again. The reason is, that the CPU of the cubietruck is at 100 % then.
@freigeist, seems NIS is busy and thus not answering fast enough. Is the processor load high when this happens?
I zip the blockchain to make it easier and faster to download, you can download it here: https://drive.bitcasa.com/send/-sd8DaCs-X_p-nNEKk2iR5UqaYRSNKRwVGXVzINoqiMj
It was done today (nov/2) a 9:00 GMT.
Extract to the nem/nis/data before starting the NIS.
@freigeist, seems NIS is busy and thus not answering fast enough. Is the processor load high when this happens?
At the time the error hapaned the processor was working on average about 40 - 50% all the time.
I had another issue with nis later after some time when everything synchronized and was running for about half hour
the processor shoot to average 70% working all time.
This time the error from before did not happend but NIS went out of sync and was always late couldn't catch up with the network.
I left it so for half hour then I closed NCC and restarted NIS and NCC and in few minutes it synched.
Since then it worked like swiss clock for few hours always beeing in synch with the network until
I closed my computer and went to sleep.
I experience this (not catching up with the blockchain) when there are 120 tx/block.
Check http://nembex.nem.ninja/ next time you see that.
Is it possible to harvest a block with zero balance? Account- TALUKXONO5ED7EJYM6A4PF6MQTQL5STTMI7C2OFE just harvested block no. 65385 with zero balance(at the moment of writing this) ??? I don't get it. Or are you testing account balance leasing ???
And all the nearby blocks have 120 txns. Can't we increase the no. of txn/block to a higher value? My txns. are taking long time to confirm.
EDIT: The account also harvested block no. 65381 ???
That is probably remote harvesting?
Is it possible to harvest a block with zero balance? Account- TALUKXONO5ED7EJYM6A4PF6MQTQL5STTMI7C2OFE just harvested block no. 65385 with zero balance(at the moment of writing this) ??? I don't get it. Or are you testing account balance leasing ???
Harvested using remote harvesting, block explorer can't show it correctly yet.
Can't we increase the no. of txn/block to a higher value?
We probably won't increase it any-time soon. 120*60*24*sizeof(transaction), you do the math.
My txns. are taking long time to confirm.
WHEN? when there are 120 TXes / block? if so increase the fee - transactions are included in block depending on a fee, higher fee = bigger chance to be included
if this happens during normal operation (< 120TX / block), we'd need more details from you.
The NIS on Linux Debian7-32 opened a lot of process and was unstable, i had to restart … here today log files queiram case take a look
[url=https://drive.bitcasa.com/send/S2uCbgQ0MuGFeFNTLBaWb1UzngE_66qOqYOL4-sqZPn5]https://drive.bitcasa.com/send/S2uCbgQ0MuGFeFNTLBaWb1UzngE_66qOqYOL4-sqZPn5
Which encryption does the .sig file uses? I'm trying to verify it programatically, but failing, needs the public key of the private key that was used for signing the files
@lcharles123:
It opened a lot of processes? Can you describe more detailed? How did you see it and what exactly?
Is it possible to harvest a block with zero balance? Account- TALUKXONO5ED7EJYM6A4PF6MQTQL5STTMI7C2OFE just harvested block no. 65385 with zero balance(at the moment of writing this) ??? I don't get it. Or are you testing account balance leasing ???
Harvested using remote harvesting, block explorer can't show it correctly yet.
Can't we increase the no. of txn/block to a higher value?
We probably won't increase it any-time soon. 120*60*24*sizeof(transaction), you do the math.
My txns. are taking long time to confirm.
WHEN? when there are 120 TXes / block? if so increase the fee - transactions are included in block depending on a fee, higher fee = bigger chance to be included
if this happens during normal operation (< 120TX / block), we'd need more details from you.
Ok, Thanks. That explains everything. And confirmations take longer only when the blocks are full. I'll send with higher fees from now on.
Various processes equal to the following:
@lcharles123:
It opened a lot of processes? Can you describe more detailed? How did you see it and what exactly?
[img width=800 height=201]http://i.imgur.com/wTzKNuo.png[/img]
But it was more than 300
Now has a 42.
running smooth here since 3 days on a Xeon E5-2660/6 gig ram/windows server 08 r2 machine.
send some TAH5BW-3DSJUP-YHV7TH-ALFIHR-HMPNA3-YFS5BG-VRHC
Which encryption does the .sig file uses? I'm trying to verify it programatically, but failing, needs the public key of the private key that was used for signing the files
pub key is in OP here: https://forum.ournem.com/alpha-launch-discussion/open-alpha-starts-now/ (just scroll bit down)
those are binary files produced by gpg, I forgot to add --armor flag, will do that in future.
You can verify it with gpg: gpg --verify nis-ncc-0.4.36.tgz.sig