[BUG] debug_traceTransaction returns "request timed out" error

[ella-quicknode]

Seid version

name: sei
server_name: <appd>
version: v5.8.0
commit: d5f2a57e21b93c8ef2690003711802cd29e762d3
build_tags: netgo,
go: go version go1.21.13 linux/amd64
build_deps:
- cosmossdk.io/[email protected]
- filippo.io/[email protected]
- github.com/99designs/[email protected]

Chain ID
Mainnet / Pacific

Describe the bug

Running this payload, you get 32002, request timed out error.
This error commonly returned when evm tx is failed.

Might be ideal to output the correct message to overcome timed out error.

{
  "jsonrpc": "2.0",
  "method": "debug_traceTransaction",
  "params": [
    "0x4650d4e40af4c738857c029ab1ebdf9d86c56541310df40f5b95a6499ccffe22",
    {
      "tracer": "callTracer",
      "timeout": "180s"
    }
  ],
  "id": 0
}

[lkim227]

Hey, it seems like you're running into a timeout issue with the debug_traceTransaction method. Basically, that 32002 error means the request is taking too long, so the system times out before it finishes.

Here’s what you can try:

Extend the timeout: Right now, you’ve set it to 180 seconds. Maybe that’s just not enough time. Try bumping it up to something like 300 seconds and see if that helps.

Look at the transaction itself: If the transaction is super complicated, that could be why it's taking forever. It might be worth checking if there’s anything in there that could be simplified.

Check the server’s performance: Sometimes this happens because the server is overloaded or low on resources. If you’re managing the server, it’s a good idea to see if there’s enough CPU or memory available to handle the request.

So, yeah, try upping the timeout and maybe check if the transaction or server performance could be causing the delay. Let me know how it goes!

[ella-quicknode]

Hi, @lkim227 thanks for the comment. The error request timed out is not relating to the timeout flag in the payload, we can add any value but error will persist. This error only returned due to the evm tx is a failed tx. This issue had been addressed with Sei team through a different channel, so having this github for tracking only. 🙂