How many peers am I connect to?

[damncourier]

@LithStud fudged the time for this one but regardless the java exception trace is out of the log. here is what i got:

2017-02-22 14:30:13 INFO: Block not accepted
2017-02-22 14:30:14 FINE: Ignoring peer broadcast block with ID 17477568179279197553. Already exists in queue

[LithStud]

@damncourier ahh expected there to be a reason, but i guess when implementing exception they didnt add the ability to take out message from it, welp at least it didnt break anything :) so its fine as is :)

[damncourier]

@LithStud yeah from the code i was expecting the same but it isn't long and scary looking so, um problem solved right?

i am still at a loss on that error i am getting on FINE logging that seems to indicate new blocks are not being excepted and the wallet being stuck. hoping to get someone to confirm the error and the behavior.

[LithStud]

@damncourier yea not sure whats that one about

[nixxda]

again! stuck at 331025

2017-02-22 21:19:54 SEVERE: Block not accepted
nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 80072496 current time is 80072394, previous block timestamp is 80072256
	at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:849)
	at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:45)
	at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

and

2017-02-22 21:21:37 FINE: Ignoring peer broadcast block with ID 1987479303904250709. Already exists in queue

time sync was turned of for a moment today! but nothing major

gona try harder!-/

[LithStud]

@nixxda its not stuck ;)

[nixxda]

@LithStud yeah, something fishy! UI is stuck thou! unfortunately I forgot to "http://127.0.0.1:8125/burst?requestType=getBlockchainStatus"

[LithStud]

@nixxda its not stuck per say, its just revert to normal 30s check too early for some reason (well basically it thinks done syncing now check normally:)

[Burstde]

Maybe same time. Plus all day today a lot of block not accepted. Last time I saw that was in 1.2.6 wallet and it
went away for me with the 1.2.7 wallet

[Burstde]

Well as soon as I added a new wallet 1.2.8 now I get this block not accepted which means sooner or later I will loose this database too

[LithStud]

@Burstde no you wont, i had not accepted blocks both in previous and this current version :) never had problems with db ;) and my pc had crashed more than once when client was running ;)

[Burstde]

@lithstud Not really sure you realize running a pool makes a difference......... as I can tell you pool is forked now

[Burstde]

This post is deleted!

[MrWho]

@luxe @Burstde @LithStud is there a fix for the "Ignoring peer broadcast block with ID XXXXXX. Already exists in queue" message? Otherwise its possible to implement a System.exit() or to say in which file it will executed the message, so it would helpful, so my batch could automatic restart the wallet if it close automatically.

[luxe]

@MrWho It is just a info, not a exception ... no need to restart. Or did your wallet does not work after that info?

[MrWho]

The pool stuck, I need to restart the wallet, its then in the correct block again, but without restart, I dont come over the block. Is there anything what I can do against this ?