How many peers am I connect to?
-
@LithStud yeah, something fishy! UI is stuck thou! unfortunately I forgot to "http://127.0.0.1:8125/burst?requestType=getBlockchainStatus"
-
@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:)
1Feel like investing long term? YASA Asset: 12143106865567593139
My Mods Discord: https://discord.gg/eEedA9Z
Send love (^_^) BURST-S94A-Z3T5-TDZT-AK6NBBitcoin Faucet: https://goo.gl/paqMVT
-
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
-
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
-
@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 ;)
0My Mods Discord: https://discord.gg/eEedA9Z
Send love (^_^) BURST-S94A-Z3T5-TDZT-AK6NBBitcoin Faucet: https://goo.gl/paqMVT
-
@lithstud Not really sure you realize running a pool makes a difference......... as I can tell you pool is forked now
-
This post is deleted!
-
@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.
-
@MrWho It is just a info, not a exception ... no need to restart. Or did your wallet does not work after that info?
-
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 ?
