Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

debug_traceTransaction breaking the node #1806

Closed
tclemos opened this issue Mar 13, 2023 · 3 comments · Fixed by #1811
Closed

debug_traceTransaction breaking the node #1806

tclemos opened this issue Mar 13, 2023 · 3 comments · Fixed by #1811
Assignees
Labels
blue-berry bug Something isn't working rpc

Comments

@tclemos
Copy link
Contributor

tclemos commented Mar 13, 2023

const txHash = "0xb6a8741e3dd6da5f49b15a3dfdab08e71c1fc3d2f49feef11e5ae1c4d0a4f603";
const res = await provider.send("debug_traceTransaction", [txHash]);
console.log(res);

The RPC seems to crashes with the next error:

Error: processing response error (body="{\"jsonrpc\":\"2.0\",\"id\":42,\"error\":{\"code\":-32000,\"message\":\"failed to get trace\"}}", error={"code":-32000}, requestBody="{\"method\":\"debug_traceTransaction\",\"params\":[\"0xb6a8741e3dd6da5f49b15a3dfdab08e71c1fc3d2f49feef11e5ae1c4d0a4f603\"],\"id\":42,\"jsonrpc\":\"2.0\"}", requestMethod="POST", url="https://rpc.internal.zkevm-test.net/", code=SERVER_ERROR, version=web/5.7.1)
@tclemos tclemos added bug Something isn't working rpc labels Mar 13, 2023
@tclemos tclemos self-assigned this Mar 13, 2023
@tclemos tclemos changed the title eth_traceTransaction breaking the node debug_traceTransaction breaking the node Mar 13, 2023
@ymonye
Copy link

ymonye commented Aug 24, 2023

Hi, how do you enable the debug_* api on a zkEVM node? I couldn't find those settings in the doc, and seems it's disabled by default (at least for me).

@tclemos
Copy link
Contributor Author

tclemos commented Aug 24, 2023

Hi, how do you enable the debug_* api on a zkEVM node? I couldn't find those settings in the doc, and seems it's disabled by default (at least for me).

hi @ymonye, you need to set the --http.api flag with all the API groups you want exposed by the jRPC Server, here is an example:

- "/app/zkevm-node run --network custom --custom-network-file /app/genesis.json --cfg /app/config.toml --components rpc --http.api eth,net,debug,zkevm,txpool,web3"

@ymonye
Copy link

ymonye commented Aug 24, 2023

--http.api eth,net,debug,zkevm,txpool,web3

Thank you so much! That worked. I really appreciate you getting back to me as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blue-berry bug Something isn't working rpc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants