Sync data returned unknown top block #66
Comments
|
Hi All the time is same error even with wallet GUI Regards |
|
Maybe someone continues to mine on the not zawy chain |
|
What is your target speed? If it's too low (ie 60-90 seconds), and the network cannot sync quickly enough, or one of your seed nodes went offline that contain the signatures you need to verify the block, you will get failed to sync because of the ring signatures not being valid for the block. If you "set_log 4" you should see "Failed to verify ring signature" for the given block. "Alternate chains" mean that your target speed is too low and the chain cannot keep up with re-arranging the blocks into a coherent verifiable chain. The lower your target speed, the smaller your community capable of using the crypto and vice-versa. Know the source pretty well, have re-written the CryptoNote sources from scratch, GUI wallet and all (no QT.... & minus the bugs and wrong data-type conversions found in the C CryptoNote sources also) ;-) Try a speed of 120 or 240, and the issue should disappear (You'll need a fresh blockchain...new genesis_tx (to prevent old nodes from injecting invalid blocks back into the new chain and breaking it again.)) If you want a 'quick-fix' just copy the blockchain from a synched node to your local blockchain folder. You can quickly check the block height of a chain by visiting it's URL as such: http://domain.orIP.com:PortNumberForNode/getheight. Upon reloading the node, it will generate block indexes for the updated chain, and resume as usual. If you need help PM me. |
|
I have just one issue with gui wallet. Synchronizationstate.cpp not sure
how to fix properly i can chnage on bit about genesis push back so gui will
open amd sync but it wont lock in. I always get void size == height
…On Mar 14, 2018 08:10, "Matthew Combatti" ***@***.***> wrote:
What is your target speed? If it's too low (ie 60-90 seconds), and the
network cannot sync quickly enough, or one of your seed nodes went offline
that contain the signatures you need to verify the block, you will get
failed to sync because of the ring signatures not being valid for the
block. If you "set_log 4" you should see "Failed to verify ring signature"
for the given block. "Alternate chains" mean that your target speed is too
low and the chain cannot keep up with re-arranging the blocks into a
coherent verifiable chain. The lower your target speed, the smaller your
community capable of using the crypto and vice-versa. Know the source
pretty well, have re-written the CryptoNote sources from scratch, GUI
wallet and all (no QT.... & minus the bugs and wrong data-type conversions
found in the C CryptoNote sources also) ;-) Try a speed of 120 or 240, and
the issue should disappear (You'll need a fresh blockchain...new genesis_tx
(to prevent old nodes from injecting invalid blocks back into the new chain
and breaking it again.)) If you want a 'quick-fix' just copy the blockchain
from a synched node to your local blockchain folder. You can quickly check
the block height of a chain by visiting it's URL as such:
http://domain.orIP.com:PortNumberForNode/getheight. Upon reloading the
node, it will generate block indexes for the updated chain, and resume as
usual. If you need help PM me.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#66 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWDragXMt5DmG6LmAzKk6z5IRp353knDks5teTLugaJpZM4SS_QA>
.
|
|
Hi And you wrote that i need to download block chain, start node with command --print-genesis-tx and will be printed new genesis but what about old chain ?? that is piece of log from my node regards |
|
What port is your node running on? Can you see the daemon output from http://ip:port/getheight |
|
Core busy (&unknown top block) - stop a running node that has the updated current blockchain. Copy that blockchain folder quickly (zip -r bc.zip ./blockchainfolder) and start that node back up so will remain current. Copy that zip to your "broken node" and replace the existing blockchain folder with the working blockchain. Start the "broken node," and wallah! It'll index the new chain and begin running... With a 50k chain...wait at least 3...4 minutes before trying to connect a wallet etc... If your node times out whole trying to connect to that url I specified, then your node is not running in daemon mode, and is not properly syncing. You will need to stop and restart the node specifying the daemon RPC bind port parameter and wait for a successful sync. You can watch a blockchain sync using set_log 3 |
|
Hi Even when I use forknote with conf. And to be honest I need help :) |
|
And the biggest issue is when wallet GUI is sync to the last known height and after is switching on alternative chain :( |
|
Nods are always chose block chain with bigger difficulty, when some one mess with mine block chain the speed go up from kh/s to ph/s and difficulty jump as wall... that's why nods always switch on this block chain even if is alternative :( |
Hi
After I add Zawy dificulty algorithm to my source, some time was fine. But after around week, on my pool's height of block was 100 more then on two other running by community. Whet I checked my nods i get message then Alternative block chain block has been added to block chain, I know then that is possible only when in coin is Marriage mining but not in Bytecoin with was mine source. And now I have big issue with Sync Nods like you see below, and also I head problem to run pool again with error what was described in forknote/forknote#42.
The text was updated successfully, but these errors were encountered: