Author Topic: Cannot sync a node working on public testnet  (Read 273 times)

0 Members and 1 Guest are viewing this topic.

Offline zenwarr

  • Newbie
  • *
  • Posts: 4
    • View Profile
Cannot sync a node working on public testnet
« on: December 19, 2018, 12:36:28 pm »
Hello!

What I'm trying to do is to restore a node working on public testnet.
It cannot sync blocks past 22668516 (created on 6 dec).

I start the node and after some time it gets stuck in infinite loop failing to push blocks:

Code: [Select]
2805054ms th_a       main.cpp:141                  main                 ] Started BitShares node on a chain with 22668516 blocks.
2805055ms th_a       main.cpp:142                  main                 ] Chain ID is 39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447
2805143ms th_a       db_block.cpp:210              _push_block          ] Failed to push new block:
3070000 undo_database_exception: undo database exception
The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you would like to continue applying blocks beyond this point.
    {"last_irreversible_block_num":22658517,"head":22668517,"recently_missed":181474,"max_undo":10000}
    th_a  db_update.cpp:77 update_global_dynamic_data

    {"next_block.block_num()":22668517}
    th_a  db_block.cpp:606 _apply_block
2805143ms th_a       application.cpp:538           handle_block         ] Error when pushing block:
3070000 undo_database_exception: undo database exception
The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you would like to continue applying blocks beyond this point.
    {"last_irreversible_block_num":22658517,"head":22668517,"recently_missed":181474,"max_undo":10000}
    th_a  db_update.cpp:77 update_global_dynamic_data

    {"next_block.block_num()":22668517}
    th_a  db_block.cpp:606 _apply_block

    {"new_block":{"previous":"0159e4e42fe6160a9ed2ef5c61f68ed901e82412","timestamp":"2018-12-06T10:35:00","witness":"1.6.8","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"20357aa8fac292cabbc617462c5899f73fb78acc0c41153239fa19bb25bf8001674c1dc8714abdfcc915aa09f91bd129ce1fbcaa6516831dd0f156375745849f19","transactions":[]}}
    th_a  db_block.cpp:219 _push_block
2805143ms th_a       fork_database.cpp:64          push_block           ] Pushing block to fork database that failed to link: 0159e4e600cb149e22ef960442ca331159914617, 22668518
2805143ms th_a       fork_database.cpp:65          push_block           ] Head: 22668516, 0159e4e42fe6160a9ed2ef5c61f68ed901e82412
2805143ms th_a       application.cpp:533           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:85 _push_block

    {"new_block":{"previous":"0159e4e579f49d76d221e5a756a88b38dc7ee9a2","timestamp":"2018-12-06T10:35:30","witness":"1.6.6","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"202de9ffda508da5731c86a93f05e830d7d5f527ef2ee9e1211b89e424acf95def09ab447d008fe8e6c880bb8668c97218848b96e7577704f7b1f51b5a4310366f","transactions":[]}}
    th_a  db_block.cpp:219 _push_block

After it the node tries to push some number of blocks, fails and tries to push them again.

The node is already upgraded to the latest version (built from github testnet branch, test-2.0.181128).
What I've already tried to do:
1. Replaying blockchain by starting with `--replay-blockchain` flag
2. Removing the entire data directory and syncing from scratch.
3. Setting checkpoints on failed blocks

I've tried to find any info on increasing undo history size too, but without success.

Can anyone point me to the possible source of the problem and ways to solve it?

Online Bangzi

  • Sr. Member
  • ****
  • Posts: 233
    • View Profile
    • Steemit: Bangzi
  • BitShares: bangzi
Re: Cannot sync a node working on public testnet
« Reply #1 on: December 19, 2018, 12:39:48 pm »
Please use these checkpoints:
--checkpoint=[22668517,0159e4e579f49d76d221e5a756a88b38dc7ee9a2]
--checkpoint=[22668518,0159e4e600cb149e22ef960442ca331159914617]

Redo step 2: 2. Removing the entire data directory and syncing from scratch.

Please Vote for My Witness: Bangzi
请投票支持比特股见证人: Bangzi
Witness Update: https://bitsharestalk.org/index.php?topic=26459.0

Offline zenwarr

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: Cannot sync a node working on public testnet
« Reply #2 on: December 19, 2018, 02:46:02 pm »
Thank you, it works!