From 2b82a11bcfa7687273fea223b5025a35a1a733d3 Mon Sep 17 00:00:00 2001 From: squidbear <379651+czarly@users.noreply.github.com> Date: Sat, 29 Mar 2025 08:27:45 +0100 Subject: [PATCH] fix --- .../reth/berachain-bepolia-reth-archive-trace.yml | 12 +++++++++++- .../reth/berachain-bepolia-reth-pruned-trace.yml | 12 +++++++++++- .../reth/berachain-mainnet-reth-archive-trace.yml | 12 +++++++++++- .../reth/berachain-mainnet-reth-pruned-trace.yml | 12 +++++++++++- 4 files changed, 44 insertions(+), 4 deletions(-) diff --git a/berachain/reth/berachain-bepolia-reth-archive-trace.yml b/berachain/reth/berachain-bepolia-reth-archive-trace.yml index 8777e8f0..39c05717 100644 --- a/berachain/reth/berachain-bepolia-reth-archive-trace.yml +++ b/berachain/reth/berachain-bepolia-reth-archive-trace.yml @@ -1,3 +1,14 @@ +# this is what you should know: +# the execution client can not start before the node part initialized and generated a genesis block for the execution client +# once the execution client is started it needs a push from the node to start syncing but then syncs p2p +# if you restart the node then the node willnot start anymore because the execution client is syncing +# but the execution client stops syncing if it doesn't get a node to push it. +# delete and resync. idk what's the solution honestly + +# rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive + +# I also suspect that the peers will blacklist you frequently if you try more than once + services: berachain-bepolia-archive: image: ghcr.io/paradigmxyz/reth:${RETH_VERSION:-v1.3.4} @@ -65,7 +76,6 @@ services: - "CHAINNAME=bepolia" - "CHAINID=80069" - "AUTH_RPC=http://berachain-bepolia-archive:8551" - - "AUTH_RPC=http://berachain-bepolia-archive:8545" - "CHAIN_SPEC=testnet" entrypoint: [ "sh", "/init.sh" ] networks: diff --git a/berachain/reth/berachain-bepolia-reth-pruned-trace.yml b/berachain/reth/berachain-bepolia-reth-pruned-trace.yml index ef01a9b9..e81cc0bb 100644 --- a/berachain/reth/berachain-bepolia-reth-pruned-trace.yml +++ b/berachain/reth/berachain-bepolia-reth-pruned-trace.yml @@ -1,3 +1,14 @@ +# this is what you should know: +# the execution client can not start before the node part initialized and generated a genesis block for the execution client +# once the execution client is started it needs a push from the node to start syncing but then syncs p2p +# if you restart the node then the node willnot start anymore because the execution client is syncing +# but the execution client stops syncing if it doesn't get a node to push it. +# delete and resync. idk what's the solution honestly + +# rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive + +# I also suspect that the peers will blacklist you frequently if you try more than once + services: berachain-bepolia: image: ghcr.io/paradigmxyz/reth:${RETH_VERSION:-v1.3.4} @@ -65,7 +76,6 @@ services: - "CHAINNAME=bepolia" - "CHAINID=80069" - "AUTH_RPC=http://berachain-bepolia:8551" - - "AUTH_RPC=http://berachain-bepolia:8545" - "CHAIN_SPEC=testnet" entrypoint: [ "sh", "/init.sh" ] networks: diff --git a/berachain/reth/berachain-mainnet-reth-archive-trace.yml b/berachain/reth/berachain-mainnet-reth-archive-trace.yml index bedcf11c..68b9e635 100644 --- a/berachain/reth/berachain-mainnet-reth-archive-trace.yml +++ b/berachain/reth/berachain-mainnet-reth-archive-trace.yml @@ -1,3 +1,14 @@ +# this is what you should know: +# the execution client can not start before the node part initialized and generated a genesis block for the execution client +# once the execution client is started it needs a push from the node to start syncing but then syncs p2p +# if you restart the node then the node willnot start anymore because the execution client is syncing +# but the execution client stops syncing if it doesn't get a node to push it. +# delete and resync. idk what's the solution honestly + +# rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive + +# I also suspect that the peers will blacklist you frequently if you try more than once + services: berachain-mainnet-archive: image: ghcr.io/paradigmxyz/reth:${RETH_VERSION:-v1.3.4} @@ -65,7 +76,6 @@ services: - "CHAINNAME=mainnet" - "CHAINID=80094" - "AUTH_RPC=http://berachain-mainnet-archive:8551" - - "AUTH_RPC=http://berachain-mainnet-archive:8545" - "CHAIN_SPEC=mainnet" entrypoint: [ "sh", "/init.sh" ] networks: diff --git a/berachain/reth/berachain-mainnet-reth-pruned-trace.yml b/berachain/reth/berachain-mainnet-reth-pruned-trace.yml index 2a40073e..16a9ad4d 100644 --- a/berachain/reth/berachain-mainnet-reth-pruned-trace.yml +++ b/berachain/reth/berachain-mainnet-reth-pruned-trace.yml @@ -1,3 +1,14 @@ +# this is what you should know: +# the execution client can not start before the node part initialized and generated a genesis block for the execution client +# once the execution client is started it needs a push from the node to start syncing but then syncs p2p +# if you restart the node then the node willnot start anymore because the execution client is syncing +# but the execution client stops syncing if it doesn't get a node to push it. +# delete and resync. idk what's the solution honestly + +# rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive + +# I also suspect that the peers will blacklist you frequently if you try more than once + services: berachain-mainnet: image: ghcr.io/paradigmxyz/reth:${RETH_VERSION:-v1.3.4} @@ -65,7 +76,6 @@ services: - "CHAINNAME=mainnet" - "CHAINID=80094" - "AUTH_RPC=http://berachain-mainnet:8551" - - "AUTH_RPC=http://berachain-mainnet:8545" - "CHAIN_SPEC=mainnet" entrypoint: [ "sh", "/init.sh" ] networks: