BitShares Forum
Main => Technical Support => Topic started by: Troglodactyl on January 30, 2016, 08:24:30 pm
-
I've attempted to resync a number of times today and keep stalling out with this:
1270591ms th_a application.cpp:525 handle_block ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
{}
th_a fork_database.cpp:81 _push_block
{"new_block":{"previous":"002ed047b2c977366e45ec5164ae95d2ae84bb97","timestamp":"2016-01-29T01:37:33","witness":"1.6.17","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"204303bc91c8cb28cdcc38575ec9547f0dc4970170b831683c75f1f0abbf92d48136505af995804ab9bea416a5f90afe96b7db762fc2dfc033f36083416b9f4d47","transactions":[]}}
th_a db_block.cpp:201 _push_block
1270591ms th_a fork_database.cpp:60 push_block ] Pushing block to fork database that failed to link: 002ed049662d95b06d7e8164b27e204b113511ba, 3067977
1270591ms th_a fork_database.cpp:61 push_block ] Head: 3067959, 002ed0373fd510a23b375e022c62154499b35bbe
1270591ms th_a application.cpp:525 handle_block ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
{}
th_a fork_database.cpp:81 _push_block
{"new_block":{"previous":"002ed0480aea3c92bd537999d865cc7cb3c0a54e","timestamp":"2016-01-29T01:37:42","witness":"1.6.35","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f5d8a0a03d97498a1d501e39510cec4e92d3db093d5e24cba4b3ab5b09b5661a764686113e417c2753377c6bb7f77d0a39af0231f67ed7fda285477f52145697f","transactions":[]}}
th_a db_block.cpp:201 _push_block
1270591ms th_a fork_database.cpp:60 push_block ] Pushing block to fork database that failed to link: 002ed04a061430c5daec0f233e6b2147e05d0768, 3067978
1270591ms th_a fork_database.cpp:61 push_block ] Head: 3067959, 002ed0373fd510a23b375e022c62154499b35bbe
1270591ms th_a application.cpp:525 handle_block ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
{}
th_a fork_database.cpp:81 _push_block
{"new_block":{"previous":"002ed049662d95b06d7e8164b27e204b113511ba","timestamp":"2016-01-29T01:37:45","witness":"1.6.49","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f71078310ac9dcff2b706d275e3b365d4a6637d00da692d1b5c9be87ca708200307fe0e61ccf1a82dc92472442377ad6be2d8d4e163fd5b66ee5042c369828912","transactions":[]}}
th_a db_block.cpp:201 _push_block
1270592ms th_a fork_database.cpp:60 push_block ] Pushing block to fork database that failed to link: 002ed04bb1ee8f9843fed2aa9054f76bf75425a1, 3067979
1270592ms th_a fork_database.cpp:61 push_block ] Head: 3067959, 002ed0373fd510a23b375e022c62154499b35bbe
Any ideas?
-
Upgrade to newest release please.
-
I'm running the winx64-cli-tool.exe that was put out just an hour ago and I'm getting the same "unlinkable-block"
It catches up and then stalls out, over and over again.
2801963ms th_a application.cpp:525 handle_block ] Error
when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
{}
th_a fork_database.cpp:81 graphene::chain::fork_database::_push_block
{"new_block":{"previous":"002f962ff67b4ae68af73d7d64c9d55d551dd707","timesta
mp":"2016-01-31T00:46:24","witness":"1.6.38","transaction_merkle_root":"00000000
00000000000000000000000000000000","extensions":[],"witness_signature":"206e44a57
4651ef4c4748f7e5271f0c4559433af9f5bf0bd52d7e110a1d2642e2c57844a1310291644a3be044
06eb73f50870bdbfffb4fdaaa96a3f41e5d369e53","transactions":[]}}
th_a db_block.cpp:201 graphene::chain::database::_push_block
I had a similar issue a month ago and then it went away. Now its back again.
-
My witness_node works fine under windows. Started with --replay-blockchain.
-
My witness_node works fine under windows. Started with --replay-blockchain.
Yes, I started with --replay also.
Maybe its something to do with my VPN. But I havn't change anything with that and it was working perfectly before. IDK
-
Got synced. I re-checked out the latest tag and rebuilt (again) in RelWithDebInfo mode. Not sure if I wasn't really on latest before or if something else was going on, but thanks.
-
I'm running the winx64-cli-tool.exe that was put out just an hour ago and I'm getting the same "unlinkable-block"
It catches up and then stalls out, over and over again.
2801963ms th_a application.cpp:525 handle_block ] Error
when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
{}
th_a fork_database.cpp:81 graphene::chain::fork_database::_push_block
{"new_block":{"previous":"002f962ff67b4ae68af73d7d64c9d55d551dd707","timesta
mp":"2016-01-31T00:46:24","witness":"1.6.38","transaction_merkle_root":"00000000
00000000000000000000000000000000","extensions":[],"witness_signature":"206e44a57
4651ef4c4748f7e5271f0c4559433af9f5bf0bd52d7e110a1d2642e2c57844a1310291644a3be044
06eb73f50870bdbfffb4fdaaa96a3f41e5d369e53","transactions":[]}}
th_a db_block.cpp:201 graphene::chain::database::_push_block
I had a similar issue a month ago and then it went away. Now its back again.
For anyone on Windows having this issue I think I may have solved it. At least it seems that way so far.
It appears to be a windows time sync issue.
If you've never set it yourself time sync is likely set to manual, it should be set to Automatic.
To do this:
>click Start> type "services" > select "Services" from the list > double click "Windows Time" from the services list
> change startup type to "Automatic" > Click Apply >
you may then need to start the service if it is not already running.
And thats it. After some time the witness_node will catch up, time will sync, and you should be good to go.
no more unlinkable blocks
Heres a video describing the Windows Time process:
https://www.youtube.com/watch?v=JJL6geu7ovk
[update]: Spoke to soon :( I do still get the unlinkable block errors and occasional hangs but a lot less frequent.
[update2]: seems to have zero effect. getting unlinkable block all the time now. Gets stuck for HOURS! .. really annoying. I can't figure it out.