[Failed-Request-Alert-Tuning] eth_getBlockByHash && eth_getBlockByNumber method returns too many 500 errors

[quiet-node]

Problem

• Approximately 60,000 log entries on mainnet display the error: Received an invalid integer type: null, without providing additional diagnostic details. This issue is a major contributor to 500 errors for both eth_getBlockByHash and eth_getBlockByNumber. The root cause stems from the shared EthImpl.getBlock() method used by both endpoints. The closest trace log indicates, Synthetic transaction hashes will be populated in the block response, suggesting that the issue arises after the populateSyntheticTransactions() process. It is likely rooted in the ReceiptsRootUtils.buildReceiptRootHashes() method or during the instantiation of a new Block().

• Another issue identified in the mainnet logs is the error: Cannot read properties of null (reading 'toString'), which occurs on eth_getBlock endpoints. This error is logged immediately after the Mirror Node (MN) call is submitted and is likely originating within the EthImpl.getBlock() method. Example Request ID: 2504dbdb-e3a4-4d6c-8f2f-af8ba8c7d05b.

Solution

Investigate and fix the underlying issue in the EthImpl.getBlock() function that causes the Internal Error, ensuring proper handling and accurate processing of block data.