search

forknote / cryptonote-generator

Generate Cryptonote coin with 1 command
104 stars 211 forks source link

Sync data returned unknown top block #66

Open servc4 opened 6 years ago

servc4 commented 6 years ago

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 https://github.com/forknote/forknote/issues/42.

2018-Feb-26 05:11:27.380095 INFO    SYNCHRONIZATION started
2018-Feb-26 05:11:27.385403 INFO    [155.133.24.233:18080 OUT] Sync data returned unknown top block: 45616 -> 45620 [4 blocks (0 days) behind]
2018-Feb-26 05:11:27.385403 INFO    SYNCHRONIZATION started
2018-Feb-26 05:11:27.477651 INFO    [31.172.137.54:18080 OUT] Sync data returned unknown top block: 45616 -> 45620 [4 blocks (0 days) behind]
2018-Feb-26 05:11:27.477651 INFO    SYNCHRONIZATION started
2018-Feb-26 05:11:27.482244 INFO    [155.133.24.233:18080 OUT] Sync data returned unknown top block: 45616 -> 45620 [4 blocks (0 days) behind]
2018-Feb-26 05:11:27.482244 INFO    SYNCHRONIZATION started
2018-Feb-26 05:11:27.607792 INFO    [85.147.35.14:18080 OUT] Sync data returned unknown top block: 45616 -> 45620 [4 blocks (0 days) behind]
2018-Feb-26 05:11:27.607792 INFO    SYNCHRONIZATION started
2018-Feb-26 05:11:29.038981 INFO    [46.147.193.168:61873 INC] Sync data returned unknown top block: 45616 -> 45620 [4 blocks (0 days) behind]
2018-Feb-26 05:11:29.038981 INFO    SYNCHRONIZATION started
2018-Feb-26 05:11:29.180026 INFO    [87.76.11.74:18080 OUT] Sync data returned unknown top block: 45616 -> 45620 [4 blocks (0 days) behind]
2018-Feb-26 05:11:29.180026 INFO    SYNCHRONIZATION started
2018-Feb-26 05:11:29.289195 INFO    [159.224.152.167:18080 OUT] Sync data returned unknown top block: 45616 -> 45620 [4 blocks (0 days) behind]
2018-Feb-26 05:11:29.289195 INFO    SYNCHRONIZATION started
servc4 commented 6 years ago

Hi Any suestions, why I am not able to sync my nods at all ?? And all the time I have same error.... I made compilation with extensions listed below. core/bytecoin.json bug-fixes.json blockchain-explorer.json print-genesis-tx.json
versionized-parameters.json zawy-difficulty-algorithm.json

All the time is same error even with wallet GUI Sync data returned unknown top block

Regards

pmitchev commented 6 years ago

Maybe someone continues to mine on the not zawy chain

simulanics commented 6 years ago

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.

3ch0elite commented 6 years ago

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" notifications@github.com 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 https://github.com/forknote/cryptonote-generator/issues/66#issuecomment-373056271, or mute the thread https://github.com/notifications/unsubscribe-auth/AWDragXMt5DmG6LmAzKk6z5IRp353knDks5teTLugaJpZM4SS_QA .

servc4 commented 6 years ago

Hi I read your message, and if target speed that is DIFFICULTY_TARGET then mine is set 120 second thing is that always is like that: 2018-Mar-14 18:20:40.082014 INFO [107.181.189.71:46530 INC] Sync data returned unknown top block: 54415 -> 55936 [1521 blocks (2 days) behind] but current height is 55935

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

2018-Mar-14 18:20:40.082014 INFO    [107.181.189.71:46530 INC] Sync data returned unknown top block: 54415 -> 55936 [1521 blocks (2 days) behind]
2018-Mar-14 18:20:40.082014 INFO    SYNCHRONIZATION started
2018-Mar-14 18:20:40.082150 DEBUG   Remote top block height: 55936, id: 48e640f88a9202c603d126d3c64fcf21387cc14ed520d564b0906e2311307a19
2018-Mar-14 18:20:40.082204 TRACE   [107.181.189.71:46530 INC] requesting synchronization
2018-Mar-14 18:20:40.082252 TRACE   Observed height updated: 55936
2018-Mar-14 18:20:40.082307 DEBUG   [107.181.189.71:46530 INC] writeHandler started
2018-Mar-14 18:20:40.251000 DEBUG   [107.181.189.71:46530 INC] Back ping connection to 107.181.189.71:18080 failed: TcpConnector::connect, connection failed
2018-Mar-14 18:20:40.251148 DEBUG   COMMAND_HANDSHAKE
2018-Mar-14 18:20:40.251215 TRACE   [107.181.189.71:46530 INC] Starting synchronization
2018-Mar-14 18:20:40.251625 TRACE   [107.181.189.71:46530 INC] -->>NOTIFY_REQUEST_CHAIN: m_block_ids.size()=18
2018-Mar-14 18:20:40.251705 DEBUG   [107.181.189.71:46530 INC] msg 1:1001
2018-Mar-14 18:20:40.251792 DEBUG   [107.181.189.71:46530 INC] msg 2:2006
2018-Mar-14 18:20:40.438067 TRACE   [107.181.189.71:46530 INC] NOTIFY_REQUEST_CHAIN: m_block_ids.size()=18
2018-Mar-14 18:20:40.444324 TRACE   [107.181.189.71:46530 INC] -->>NOTIFY_RESPONSE_CHAIN_ENTRY: m_start_height=53887, m_total_height=54415, m_block_ids.size()=528
2018-Mar-14 18:20:40.444494 DEBUG   [107.181.189.71:46530 INC] msg 2:2007
2018-Mar-14 18:20:41.069094 DEBUG   Connecting to 80.3.187.108:18080 (white=1, last_seen: never)...
2018-Mar-14 18:20:41.239425 TRACE   [107.181.189.71:46530 INC] NOTIFY_RESPONSE_CHAIN_ENTRY: m_block_ids.size()=1650, m_start_height=54286, m_total_height=55936
2018-Mar-14 18:20:41.240356 TRACE   [107.181.189.71:46530 INC] -->>NOTIFY_REQUEST_GET_OBJECTS: blocks.size()=100, txs.size()=0
2018-Mar-14 18:20:41.240460 DEBUG   [107.181.189.71:46530 INC] msg 2:2003
2018-Mar-14 18:20:41.274227 TRACE   [107.181.189.71:46530 INC] NOTIFY_REQUEST_GET_OBJECTS
2018-Mar-14 18:20:41.284825 TRACE   [107.181.189.71:46530 INC] -->>NOTIFY_RESPONSE_GET_OBJECTS: blocks.size()=75, txs.size()=0, rsp.m_current_blockchain_height=54415, missed_ids.size()=0
2018-Mar-14 18:20:41.285356 DEBUG   [107.181.189.71:46530 INC] msg 2:2004
2018-Mar-14 18:20:41.408326 TRACE   [5.150.238.54:7804 INC] COMMAND_TIMED_SYNC
2018-Mar-14 18:20:41.408455 DEBUG   [5.150.238.54:7804 INC] msg 1:1002

regards ServC4

simulanics commented 6 years ago

What port is your node running on? Can you see the daemon output from http://ip:port/getheight ?, does it timeout or say "core busy"? Each I can help you with. :-)

simulanics commented 6 years ago

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

servc4 commented 6 years ago

Hi I changed Genesis, network and p2p key but there is issue with sync.

2018-Mar-19 13:34:55.067506 INFO    [185.201.112.7:18080 OUT] Sync data returned unknown top block: 54415 -> 57744 [3329 blocks (4 days) behind]
2018-Mar-19 13:34:55.067506 INFO    SYNCHRONIZATION started
2018-Mar-19 13:34:55.067937 DEBUG   Remote top block height: 57744, id: bb6398d31a04d43d9623165b01aebb81deca0c09cc00004ce1a371dd76e9a297
2018-Mar-19 13:34:55.068167 TRACE   [185.201.112.7:18080 OUT] requesting synchronization
2018-Mar-19 13:34:55.068375 TRACE   Observed height updated: 57744
2018-Mar-19 13:34:55.068573 DEBUG   [185.201.112.7:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2018-Mar-19 13:34:55.068970 TRACE   [185.201.112.7:18080 OUT] NEW CONNECTION
2018-Mar-19 13:34:55.069186 TRACE   [185.201.112.7:18080 OUT] Starting synchronization
2018-Mar-19 13:34:55.071097 TRACE   [185.201.112.7:18080 OUT] -->>NOTIFY_REQUEST_CHAIN: m_block_ids.size()=18
2018-Mar-19 13:34:55.071360 DEBUG   [185.201.112.7:18080 OUT] writeHandler started
2018-Mar-19 13:34:55.071569 DEBUG   [185.201.112.7:18080 OUT] msg 2:2006
2018-Mar-19 13:34:55.116162 TRACE   [185.201.112.7:18080 OUT] NOTIFY_REQUEST_TX_POOL: txs.size() = 0
2018-Mar-19 13:34:55.420882 TRACE   [185.201.112.7:18080 OUT] NOTIFY_RESPONSE_CHAIN_ENTRY: m_block_ids.size()=3330, m_start_height=54414, m_total_height=57744
2018-Mar-19 13:34:55.422211 TRACE   [185.201.112.7:18080 OUT] -->>NOTIFY_REQUEST_GET_OBJECTS: blocks.size()=100, txs.size()=0
2018-Mar-19 13:34:55.422497 DEBUG   [185.201.112.7:18080 OUT] msg 2:2003
2018-Mar-19 13:34:55.704488 TRACE   [185.201.112.7:18080 OUT] NOTIFY_RESPONSE_GET_OBJECTS
2018-Mar-19 13:34:55.722596 DEBUG   Request to add block came for block d1ddfc544ab823edc9d76d25c7db6de85eff3afa89cf15b217042db1267dfe54
2018-Mar-19 13:34:55.807373 DEBUG   Block d1ddfc544ab823edc9d76d25c7db6de85eff3afa89cf15b217042db1267dfe54 has difficulty overhead
2018-Mar-19 13:34:55.807728 DEBUG   [185.201.112.7:18080 OUT] Block verification failed, dropping connection: Block difficulty overhead occurred
2018-Mar-19 13:34:55.808321 DEBUG   [185.201.112.7:18080 OUT] Interrupt connection
2018-Mar-19 13:34:55.808584 DEBUG   [185.201.112.7:18080 OUT] writeHandler finished
2018-Mar-19 13:34:55.808837 TRACE   [185.201.112.7:18080 OUT] CLOSE CONNECTION
2018-Mar-19 13:34:55.809046 TRACE   Observed height updated: 54415
2018-Mar-19 13:34:57.069176 DEBUG   Selected peer: 15903506504519706108 185.201.112.7:18080 [white=1] last_seen: d0.h00.m00.s02
2018-Mar-19 13:34:57.069538 DEBUG   Connecting to 185.201.112.7:18080 (white=1, last_seen: d0.h00.m00.s02)...

Even when I use forknote with conf.

add-exclusive-node=185.201.112.7:18080
add-exclusive-node=91.228.197.82:18080
add-exclusive-node=91.228.197.8:18080
add-exclusive-node=155.133.24.233:18080
EMISSION_SPEED_FACTOR=18
DIFFICULTY_TARGET=120
CRYPTONOTE_DISPLAY_DECIMAL_POINT=12
MONEY_SUPPLY=18446744073709551615
GENESIS_BLOCK_REWARD=0
DEFAULT_DUST_THRESHOLD=1000000000
MINIMUM_FEE=1000000000
CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW=10
CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE=100000
MAX_TRANSACTION_SIZE_LIMIT=100000
CRYPTONOTE_PUBLIC_ADDRESS_BASE58_PREFIX=73
DIFFICULTY_CUT_V1=60
DIFFICULTY_CUT_V2=60
DIFFICULTY_CUT=0
DIFFICULTY_LAG_V1=15
DIFFICULTY_LAG_V2=15
DIFFICULTY_LAG=0
DIFFICULTY_WINDOW_V1=720
DIFFICULTY_WINDOW_V2=720
DIFFICULTY_WINDOW=0
ZAWY_DIFFICULTY_BLOCK_INDEX=38500
p2p-bind-port=18080
rpc-bind-port=18081
rpc-bind-ip=0.0.0.0
BYTECOIN_NETWORK=4b597285-773c-67bd-a4da-63ee9866dcd7
CRYPTONOTE_NAME=deuter
GENESIS_COINBASE_TX_HEX=010a01ff0001ffffffffffff0f029b2e4c0281c0b02e7c53291a94d1d0cbff8883f8024f5142ee494ffbbd088071210190a45eb57e66a9396c1d048d03a39a6cb6aa92735b860e543340e020cf13079a
MAX_BLOCK_SIZE_INITIAL=100000
UPGRADE_HEIGHT_V2=1
UPGRADE_HEIGHT_V3=2
P2P_STAT_TRUSTED_PUB_KEY=d881952662992f2e4dcfcafbe57eb4d26c4df7f4ca7037950ad026f9ab36dd05

CHECKPOINT=1000:ae3488432e86698dbf6e2c9a95242c25595cca5df52bfad0623936879c986406
CHECKPOINT=4000:3ea8a554d70f5542acd5d3589ae9f0bfbf5af79e70c8261142449c82270f3942
CHECKPOINT=10000:abdabb855ec47e8f8d119612a2bdec9a277aa5d42e03a0c90d1ecfb26f87015b
CHECKPOINT=15580:86e537f9f1a80e5d113abfcc2f47a11b4baea8c1d8bb2b95018cf59d307e1bfe
CHECKPOINT=26000:761e7974ecbfd8e38adaac9004987adbe9254a2b28cec95eb41b1bccfdef6fe9
CHECKPOINT=33000:59e3719afd10919d06e8be81beb37f8e7c27acda55b5e9bd5d7b2a990769c885
CHECKPOINT=42285:7ddcdacc69ba9ee25a49703c0aaa704f84108fd1718d76b69c1d502421df5434
CHECKPOINT=45700:2d083b41ef84f3deada1bc1f7a9dd04675e6675c194997312a4d46694f3bc150
CHECKPOINT=49300:6f0c45f61b73a0ce4f01d346c75ec606110567b3900b61e98fd05a0d9e0dd012
CHECKPOINT=52100:1d160c288f78f37df740bb5b85e78516091a74398e64001ee0ce2b8a17ad5105
CHECKPOINT=53500:7ccacd9b4a710ca7fcf7ee1a2b678fc4b336eeea5a5dda70306afcc586365223
CHECKPOINT=55200:435c1bc4532dad073ffd51f514d70ac1e11264474b8ba752f2722ce0e6981742
CHECKPOINT=56000:bdfa6bf517e04f16f267ecdebd7a1ba30f8a31639773584fae471548ab5d2204
CHECKPOINT=56700:5454375959fb83b5086c25cdb65a3c2e01b242b1c28bcafa62fb93b9511940fb

And to be honest I need help :)

servc4 commented 6 years ago

And the biggest issue is when wallet GUI is sync to the last known height and after is switching on alternative chain :(

servc4 commented 6 years ago

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 :(