You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are running a Base archive node using reth and op-node. The node frequently encounters delays and never recovers, requiring a manual restart approximately once an hour. This impacts our ability to maintain a reliable archive node.
We have a script that checks the block s timestamp against and throws alerts when the node is delayed
Describe the bug
Also reported in reth
We are running a Base archive node using reth and op-node. The node frequently encounters delays and never recovers, requiring a manual restart approximately once an hour. This impacts our ability to maintain a reliable archive node.
We have a script that checks the block s timestamp against and throws alerts when the node is delayed
Hardware Specs:
Processor: AMD EPYC™ 9454P - 48 core
HDD : 3x SAMSUNG MZQL27T6HBLA-00A07
256 GB RAM: 8x SAMSUNG M321R4GA3BB6-CQKET
Environment Details
Steps to reproduce
Docker compose:
Node logs
Observed Behavior
And also I found parts of the logs with the following pattern.
Complete logs
Complete base_reth.log
Complete base_rollup_node.log
Platform(s)
Linux (x86)
Container Type
Docker
What version/commit are you on?
base_reth version : 1.1.2
base_reth image: ghcr.io/paradigmxyz/op-reth:v1.1.2
base_rollup_node version: 1.10.0
base_rollup_node image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.10.0
What database version are you on?
default
Which chain / network are you on?
base-mainnet
What type of node are you running?
Archive (default)
What prune config do you use, if any?
none
The text was updated successfully, but these errors were encountered: