Closed hazim-j closed 11 months ago
Hello @hazim-j We had same problem with full and archive nodes
Not sure what happened, we tried to make a wipe and resync, but again stucked on same block
So, we run new ec2 instance with clear node setup with this flag (--p2p.disabled), and it's fully synced with blockchain
@almukhametovd what was the rationale behind using P2P.disabled flag?
We also spun up a new EC2 instance but with same config and it synched fine.
Stale pre-bedrock issue
I'm currently trying to run an Optimism Goerli node on an AWS EC2 instance. It's been running fine and staying in sync up until recently where it started showing the following logs in the
healthcheck-bedrock
service.Any suggestions on the best way to debug this? Not sure if there's a way to rewind to before the first mismatched block?