[Node Operator Question] op-geth not syncing post upgrade and no access to debug apis #183
-
Are you running the most up to date node software?
Did you check the documentation?
Did you check for duplicate questions?
Issue Descriptionop-geth not syncing post upgrade and no access to debug apis op-node seems to be syncing debug requests coming back with: {"jsonrpc":"2.0","id":null,"error":{"code":-32600,"message":"invalid request"}} Protocol Descriptionop-node:v1.3.2 Node LogsNo response Additional InformationNo response FeedbackNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
Did you upgrade your node before the Canyon activation? |
Beta Was this translation helpful? Give feedback.
-
Hey @moorow, We hope your recent question was resolved to your satisfaction. Your feedback is invaluable and helps us improve our support services. Could you spare a moment to fill out a short feedback survey. Thank you for helping us improve our developer community. |
Beta Was this translation helpful? Give feedback.
-
@sbvegan the second issue is that I had no access to the debug api's post upgrade. Looks like the http and ws flags were being ignored.... I had to get js console access via geth to try and rollback the blocks (didn't solve it). If anyone has any ideas on this it would be very helpful. Here are the relevant flags:
Any debug request resulted in:
|
Beta Was this translation helpful? Give feedback.
Yeah those are the right versions, but because you missed the activation, you'll need to resync. Luckily we had a community contributor post a recent full node snapshot. One thing to keep in mind is that the folder structure needs to be updated after you download. You can see the full details in this PR. We have an archive snapshot here.