Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Lisk core 2.0.0-2.0.1 Failed to load block from network during syncing process

See original GitHub issue

Expected behavior

Actual behavior

Since updating to Lisk 2.0.0 sync is really slow / on-and-off.

It appears to be losing sync and catch-up a few minutes later. Latest lines from logs/mainnet/lisk.log:

{"name":"lisk-framework","hostname":"10063","pid":14413,"level":30,"msg":"Starting sync","time":"2019-07-24T18:22:35.586Z","v":0}
{"name":"lisk-framework","hostname":"10063","pid":14413,"level":50,"msg":"Failed to load block from network { RequestFailError: Request failed due to no peers found in peer selection
    at PeerPool.requestFromPeer (/home/lisk/lisk-main/node_modules/@liskhq/lisk-p2p/src/peer_pool.ts:208:10)
    at P2P.request (/home/lisk/lisk-main/node_modules/@liskhq/lisk-p2p/src/p2p.ts:379:41)
    at Object.request (/home/lisk/lisk-main/node_modules/lisk-framework/src/modules/network/network.js:267:14)
    at Object.handler (/home/lisk/lisk-main/node_modules/lisk-framework/src/modules/network/index.js:53:51)
    at InMemoryChannel.invoke (/home/lisk/lisk-main/node_modules/lisk-framework/src/controller/channels/in_memory_channel.js:118:37)
    at Bus.invoke (/home/lisk/lisk-main/node_modules/lisk-framework/src/controller/bus.js:180:48)
    at InMemoryChannel.invoke (/home/lisk/lisk-main/node_modules/lisk-framework/src/controller/channels/in_memory_channel.js:121:19)
    at getBlocksFromNetwork (/home/lisk/lisk-main/node_modules/lisk-framework/src/modules/chain/submodules/blocks/process.js:358:43)
    at /home/lisk/lisk-main/node_modules/async/dist/async.js:196:27
    at /home/lisk/lisk-main/node_modules/async/dist/async.js:74:12
    at nextTask (/home/lisk/lisk-main/node_modules/async/dist/async.js:5324:14)
    at Object.waterfall (/home/lisk/lisk-main/node_modules/async/dist/async.js:5334:5)
    at Process.loadBlocksFromNetwork (/home/lisk/lisk-main/node_modules/lisk-framework/src/modules/chain/submodules/blocks/process.js:439:8)
    at loadBlocksFromNetwork (/home/lisk/lisk-main/node_modules/lisk-framework/src/modules/chain/submodules/loader.js:813:30)
    at nextTask (/home/lisk/lisk-main/node_modules/async/dist/async.js:5324:14)
    at Object.waterfall (/home/lisk/lisk-main/node_modules/async/dist/async.js:5334:5)
  name: 'RequestFailError',
  response:
   Error: Request failed due to no peers found in peer selection
       at new RequestFailError (/home/lisk/lisk-main/node_modules/@liskhq/lisk-p2p/src/errors.ts:97:31)
       at PeerPool.requestFromPeer (/home/lisk/lisk-main/node_modules/@liskhq/lisk-p2p/src/peer_pool.ts:208:10)
       at P2P.request (/home/lisk/lisk-main/node_modules/@liskhq/lisk-p2p/src/p2p.ts:379:41)
       at Object.request (/home/lisk/lisk-main/node_modules/lisk-framework/src/modules/network/network.js:267:14)
       at Object.handler (/home/lisk/lisk-main/node_modules/lisk-framework/src/modules/network/index.js:53:51)
       at InMemoryChannel.invoke (/home/lisk/lisk-main/node_modules/lisk-framework/src/controller/channels/in_memory_channel.js:118:37)
       at Bus.invoke (/home/lisk/lisk-main/node_modules/lisk-framework/src/controller/bus.js:180:48)
       at InMemoryChannel.invoke (/home/lisk/lisk-main/node_modules/lisk-framework/src/controller/channels/in_memory_channel.js:121:19)
       at getBlocksFromNetwork (/home/lisk/lisk-main/node_modules/lisk-framework/src/modules/chain/submodules/blocks/process.js:358:43)
       at /home/lisk/lisk-main/node_modules/async/dist/async.js:196:27
       at /home/lisk/lisk-main/node_modules/async/dist/async.js:74:12
       at nextTask (/home/lisk/lisk-main/node_modules/async/dist/async.js:5324:14)
       at Object.waterfall (/home/lisk/lisk-main/node_modules/async/dist/async.js:5334:5)
       at Process.loadBlocksFromNetwork (/home/lisk/lisk-main/node_modules/lisk-framework/src/modules/chain/submodules/blocks/process.js:439:8)
       at loadBlocksFromNetwork (/home/lisk/lisk-main/node_modules/lisk-framework/src/modules/chain/submodules/loader.js:813:30)
       at nextTask (/home/lisk/lisk-main/node_modules/async/dist/async.js:5324:14),
  peerId: '',
  peerVersion: '' }","time":"2019-07-24T18:22:35.593Z","v":0}

Steps to reproduce

Which version(s) does this affect? (Environment, OS, etc…)

2.0.0, 2.0.1

Issue Analytics

State:
Created 4 years ago
Comments:8 (2 by maintainers)

Top GitHub Comments

2reactions

got3nkscommented, Aug 5, 2019

We will wait for the new version. The sync is working, albeit slowly. Thanks for the update.

2reactions

jonduboiscommented, Aug 5, 2019

@got3nks our upcoming 2.3 version fixes this problem but we can’t release it straight away because it’s missing a few features and contains a lot of other changes that need to pass through our QA process.

The use case of running a node with closed inbound ports is not well supported in 2.0.x, 2.1.x or 2.2.x. Would it be possible for you to temporarily downgrade back to the previous 1.x version (the same minor version that you were using before)?

1.x is compatible with 2.x at the P2P protocol level and has better support for your use case (with closed inbound port).

Have you made any changes to your API between 1.x and 2.x which would make downgrading difficult?

Let me know if downgrading to 1.x is suitable for you. In the meantime, I’m investigating a possible patch to 2.0.x to cover your use case.