You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
The block max payload should handle exisisting max block size of the blockchain and set the max payload size accordingly.
Actual behavior
00:19:40.036Z INFO lisk-framework: New block added to the chain (id=18329678020103194309, height=952843, numberOfTransactions=25)
00:19:40.189Z DEBUG lisk-framework: Max payload size exceeded
00:19:40.191Z DEBUG lisk-framework: INbound connection of peer 198.50.245.221:7001 was closed with code 1009 and reason:
00:19:40.191Z DEBUG lisk-framework: Message was too big to process
00:19:41.023Z DEBUG lisk-framework: Client is syncing. Can't receive block at the moment. 4202500502956161298
00:19:41.025Z DEBUG lisk-framework: Client is syncing. Can't receive block at the moment. 4202500502956161298
00:19:41.029Z DEBUG lisk-framework: Client is syncing. Can't receive block at the moment. 4202500502956161298
00:19:41.029Z DEBUG lisk-framework: Client is syncing. Can't receive block at the moment. 4202500502956161298
00:19:41.030Z DEBUG lisk-framework: Client is syncing. Can't receive block at the moment. 4202500502956161298
00:19:41.036Z DEBUG lisk-framework: Client is syncing. Can't receive block at the moment. 4202500502956161298
00:19:41.040Z DEBUG lisk-framework: Client is syncing. Can't receive block at the moment. 4202500502956161298
00:19:41.074Z DEBUG lisk-framework: Client is syncing. Can't receive block at the moment. 4202500502956161298
00:19:41.189Z DEBUG lisk-framework: Client is syncing. Can't receive block at the moment. 4202500502956161298
00:19:44.389Z DEBUG lisk-framework: Broadhash consensus: 0 %
00:19:46.657Z DEBUG lisk-framework: New inbound peer event: Connected from peer 95.179.140.193:7001 {"os":"linux4.18.0-20-generic","version":"2.0.0-rc.1","wsPort":7001,"httpPort":7000,"minVersion":"1.1.0-rc.0","protocolVersion":"1.1","height":9009274,"nethash":"da3ed6a45429278bac2666961289ca17ad86595d33b31037615d4b8e8f158bba","broadhash":"537c68c1120802dad2e4bc95e40c0a99f93588a312570c327a6a2dd5a2e3ffab","nonce":"NpULPkanMKbUmV3R","state":2,"options":"{\"os\":\"linux4.18.0-20-generic\",\"version\":\"2.0.0-rc.1\",\"wsPort\":7001,\"httpPort\":7000,\"minVersion\":\"1.1.0-rc.0\",\"protocolVersion\":\"1.1\",\"height\":9009274,\"nethash\":\"da3ed6a45429278bac2666961289ca17ad86595d33b31037615d4b8e8f158bba\",\"broadhash\":\"537c68c1120802dad2e4bc95e40c0a99f93588a312570c327a6a2dd5a2e3ffab\",\"nonce\":\"NpULPkanMKbUmV3R\",\"state\":2}","ipAddress":"95.179.140.193"}
00:19:49.402Z DEBUG lisk-framework: Broadhash consensus: 0 %
00:19:50.043Z ERROR lisk-framework: TimeoutError: Event response for 'rpc-request' timed out
00:19:50.198Z DEBUG lisk-framework: Max payload size exceeded
00:19:50.200Z DEBUG lisk-framework: INbound connection of peer 116.203.61.185:7001 was closed with code 1009 and reason:
00:19:50.200Z DEBUG lisk-framework: Message was too big to process
Steps to reproduce
Start syncing with testnet using 2.1.0-alpha.1
Which version(s) does this affect? (Environment, OS, etc...)
2.1.0
The text was updated successfully, but these errors were encountered:
Expected behavior
The block max payload should handle exisisting max block size of the blockchain and set the max payload size accordingly.
Actual behavior
Steps to reproduce
2.1.0-alpha.1
Which version(s) does this affect? (Environment, OS, etc...)
2.1.0
The text was updated successfully, but these errors were encountered: