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

Broken engine_exchangeTransitionConfigurationV1 RPC method #1486

Closed
jakubgs opened this issue Mar 6, 2023 · 2 comments · Fixed by #1676
Closed

Broken engine_exchangeTransitionConfigurationV1 RPC method #1486

jakubgs opened this issue Mar 6, 2023 · 2 comments · Fixed by #1676
Labels
bug Something isn't working RPC JSON-RPC over HTTP/websocket

Comments

@jakubgs
Copy link
Member

jakubgs commented Mar 6, 2023

The beacon-node-sepolia-unstable-trial-0 node on linux-01.he-eu-hel1.nimbus.sepolia currently fails to start with:

{"lvl":"ERR","ts":"2023-03-06 09:46:10.586+00:00","msg":"Failed to exchange transition configuration","topics":"elmon","url":"ws:https://localhost:9568","err":"{\"code\":-32601,\"message\":\"'engine_exchangeTransitionConfigurationV1' is not a registered RPC method\",\"data\":null}"}
{"lvl":"FAT","ts":"2023-03-06 09:46:10.586+00:00","msg":"The Bellatrix hard fork requires the beacon node to be connected to a properly configured Engine API end-point. See https://nimbus.guide/merge.html for more details.","topics":"elmon"}

Which means that nimbus-eth1 running for the CL node is missing the correct support for Bellatrix fork.

jakubgs added a commit to status-im/infra-nimbus that referenced this issue Mar 6, 2023
jakubgs added a commit to status-im/infra-role-nimbus-eth1 that referenced this issue Mar 6, 2023
@jakubgs
Copy link
Member Author

jakubgs commented Mar 6, 2023

Based on advice from @jangko I switched to using the Engine API WS port:

But now the result is just the fatal failure:

{"lvl":"FAT","ts":"2023-03-06 10:30:53.429+00:00","msg":"The Bellatrix hard fork requires the beacon node to be connected to a properly configured Engine API end-point. See https://nimbus.guide/merge.html for more details.","topics":"elmon"}

But I guess the issue with missing engine_exchangeTransitionConfigurationV1 was not related to the ultimate failure state.

@jakubgs
Copy link
Member Author

jakubgs commented Mar 6, 2023

Actually, the error is still there, it just changed to invalid format string:

{                                                                                                                                      
  "lvl": "ERR",
  "ts": "2023-03-06 10:33:13.109+00:00",
  "msg": "Failed to exchange transition configuration",
  "topics": "elmon",
  "url": "ws:https://localhost:8573",
  "err": "{\"code\":-32000,\"message\":\"engine_exchangeTransitionConfigurationV1 raised an exception\",\"data\":\"invalid format string\"}"
}

So the method is not actually missing.

@jakubgs jakubgs changed the title Missing engine_exchangeTransitionConfigurationV1 RPC method Broken engine_exchangeTransitionConfigurationV1 RPC method Mar 6, 2023
@jangko jangko added bug Something isn't working RPC JSON-RPC over HTTP/websocket labels Jun 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working RPC JSON-RPC over HTTP/websocket
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants