unlinkable block exception

[AceLuodan]

when i run TEStnet，I met a problem，unlinkable block exception at "head_block_num": 1310498

[AceLuodan]

2018-08-01T02:59:41.176 thread-0 controller.cpp:889 apply_block ] e.to_detail_string(): 3030000 block_validate_exception: Block exception
receipt does not match
{"producer_receipt":{"status":"soft_fail","cpu_usage_us":4248,"net_usage_words":0,"trx":[0,"6929422a066f4c59a0427c330e66eb8d31890778f706f045651c8cc386a3a2b8"]},"validator_receipt":{"status":"executed","cpu_usage_us":4248,"net_usage_words":6,"trx":[0,"6929422a066f4c59a0427c330e66eb8d31890778f706f045651c8cc386a3a2b8"]}}
thread-0 controller.cpp:876 apply_block
2018-08-01T02:59:41.178 thread-0 controller.cpp:913 push_block ] 3030000 block_validate_exception: Block exception
receipt does not match
{"producer_receipt":{"status":"soft_fail","cpu_usage_us":4248,"net_usage_words":0,"trx":[0,"6929422a066f4c59a0427c330e66eb8d31890778f706f045651c8cc386a3a2b8"]},"validator_receipt":{"status":"executed","cpu_usage_us":4248,"net_usage_words":6,"trx":[0,"6929422a066f4c59a0427c330e66eb8d31890778f706f045651c8cc386a3a2b8"]}}
thread-0 controller.cpp:876 apply_block

{}
thread-0  controller.cpp:893 apply_block

2018-08-01T02:59:41.179 thread-0 producer_plugin.cpp:306 on_incoming_block ] 3030000 block_validate_exception: Block exception
receipt does not match
{"producer_receipt":{"status":"soft_fail","cpu_usage_us":4248,"net_usage_words":0,"trx":[0,"6929422a066f4c59a0427c330e66eb8d31890778f706f045651c8cc386a3a2b8"]},"validator_receipt":{"status":"executed","cpu_usage_us":4248,"net_usage_words":6,"trx":[0,"6929422a066f4c59a0427c330e66eb8d31890778f706f045651c8cc386a3a2b8"]}}
thread-0 controller.cpp:876 apply_block

[AceLuodan]

please give me some suggestion!!!!!

[lcgogo]

Met the same issue, the jungle testnet work stop sync block at 1310498

{"server_version":"7412253f","chain_id":"038f4b0fc8ff18a4f0842a8f0564611f6e96e8535901dd45e43ac8691a1c4dca","head_block_num":1310498,"last_irreversible_block_num":1305367,"last_irreversible_block_id":"0013eb171ef2f81fcc2140dd24af50034dde0f3e70d1491974b10c036aaf92bb","head_block_id":"0013ff22028b05c04d545b7a74b9a462967eb5e764d1359db4857e2b58a33e75","head_block_time":"2018-06-18T09:34:58.000","head_block_producer":"dutcheosioxx","virtual_block_cpu_limit":200000000,"virtual_block_net_limit":1048576000,"block_cpu_limit":200000,"block_net_limit":1048576}

[spebern]

same issue here

[AceLuodan]

i think the problem is about data.

[lcgogo]

I will try the method in README. downgrade to 1.1.0 --> sync --> upgrade to 1.1.1

!!! If you are Not synced, you need to downgrade to v1.1.0 sync node and upgrade:

stop node.
downgrade to v1.1.0
remove blocks/reverrsible folder.
disable bnet /mongo plugin
update peers in config
./start.sh --replay
Upgrade to v1.1.1

[gs201510]

@lcgogo is that woks? I hava the same problem.

[lcgogo]

@gs201510 好使。

[gs201510]

@lcgogo thx, I will try

[gs201510]

downgrade nodeos to v1.1.0 works!

[toonevdb]

Had the same problem. With a version more recent than v1.1.0 I had this exception around block 3.000.000. After I downgraded, synchronization continued up to a block in the 10.000.000 but then this exception occurred again.

Solution for me was:

1. Build v1.1.0 and start nodeos ( --genesis-json genesis.json --delete-all-blocks to start fresh)
2. Let it sync to around block 10.000.000 (don't know the exact required block nr, but did it around that number)
3. Stop nodeos (ctrl+c)
4. Build v1.2.2 and start nodeos (WITHOUT --genesis-json and --delete-all-blocks)

But I have no idea to the cause or why switching versions is needed.

[nnikka]

@toonevdb
That way, worked for me as well

[Cren700]

yeah， I hava the same problem。get the V1.1.0 branch and start nodeos. The 1310498 block still Unlinkable block. Help, @toonevdb @nnikka