Closed astudnev closed 4 months ago
note that the node is not re-starting, not issuing any errors. Also we checked that it synced to mainnet correctly by matching block hashes ( they are visible in log as well )
Can you please send the op-node startup parameters?
System information
Network:
mainnet
op-node version:v0.3.1
op-geth version:v0.3.0
OS & Version: LinuxExpected behaviour
After node is synced, it continues to follow the head
Actual behaviour
Sometimes it switches to 3-6 hours old block and re-sync again, which takes up to one hour
Steps to reproduce the behaviour
we run the node using snap sync method
This happens after some time ( 12-24 hours ) that the node issues the WARN Ignoring already known beacon payload and then according to the log below catches up in 6-3 hours ago
Backtrace
at the same time op-node has one error ( L1 Info transaction differs ):