Issue with Ethereum Gateway Returning Errors on Sepolia Network Queries

General
1

What is the name of the domain?

What is the issue you’re encountering

I’m encountering an issue with Cloudflare’s Web3(Ethereum Gateway) when querying transaction information on the Sepolia network using the eth_getTransactionByHash method. Initially, the response is null, but on retrying, I receive an error with code -32000 and a detailed message suggesting potential disk space issues or hardware failure in the backend infrastructure.

What are the steps to reproduce the issue?

  1. Use the following curl command to send a request to the Ethereum Gateway:
    curl --location 'https://{MY_DOMAIN}/v1/sepolia' \
--header 'Content-Type: application/json' \
--data '{
    "jsonrpc": "2.0",
    "method": "eth_getTransactionByHash",
    "params": [
        "0xba97a..."
    ],
    "id": 1
}'
  2. Observe the response. The first request typically returns:
    {
    "jsonrpc": "2.0",
    "result": null,
    "id": 1
}
  3. Retry the same request, and observe the error response:
    {
    "jsonrpc": "2.0",
    "id": 1,
    "error": {
        "code": -32000,
        "message": "mdbx_txn_begin: MDBX_PANIC: Maybe free space is over on disk. Otherwise it's hardware failure. Before creating issue please use tools like https://www.memtest86.com to test RAM and tools like https://www.smartmontools.org to test Disk. To handle hardware risks: use ECC RAM, use RAID of disks, run multiple application instances (or do backups). If hardware checks passed - check FS settings - 'fsync' and 'flock' must be enabled.  Otherwise - please create issue in Application repo. On default DURABLE mode, power outage can't cause this error. On other modes - power outage may break last transaction and mdbx_chk can recover db in this case, see '-t' and '-0|1|2' options., label: txpool, trace: [kv_mdbx.go:606 txpool_grpc_server.go:265 txpool_client.go:52 eth_txs.go:89 value.go:596 value.go:380 service.go:224 handler.go:532 handler.go:482 handler.go:421 handler.go:241 handler.go:334 asm_amd64.s:1695]"
    }
}
  4. Cross-verify by sending the same request to a different Ethereum RPC provider, which returns the expected transaction information successfully.
2

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.