diff --git a/berachain/reth/berachain-bepolia-reth-archive-trace.yml b/berachain/reth/berachain-bepolia-reth-archive-trace.yml index 39c05717..3dec15aa 100644 --- a/berachain/reth/berachain-bepolia-reth-archive-trace.yml +++ b/berachain/reth/berachain-bepolia-reth-archive-trace.yml @@ -1,9 +1,10 @@ # 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 +# those config files are stored in ./berachain//config # 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 +# if you restart the beacon node while the execution client is syncing the beacon node will crash loop until sync is done + +# delete and resync: # rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive diff --git a/berachain/reth/berachain-bepolia-reth-pruned-trace.yml b/berachain/reth/berachain-bepolia-reth-pruned-trace.yml index e81cc0bb..8153bcd5 100644 --- a/berachain/reth/berachain-bepolia-reth-pruned-trace.yml +++ b/berachain/reth/berachain-bepolia-reth-pruned-trace.yml @@ -1,9 +1,10 @@ # 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 +# those config files are stored in ./berachain//config # 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 +# if you restart the beacon node while the execution client is syncing the beacon node will crash loop until sync is done + +# delete and resync: # rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive diff --git a/berachain/reth/berachain-mainnet-reth-archive-trace.yml b/berachain/reth/berachain-mainnet-reth-archive-trace.yml index 68b9e635..42b3f059 100644 --- a/berachain/reth/berachain-mainnet-reth-archive-trace.yml +++ b/berachain/reth/berachain-mainnet-reth-archive-trace.yml @@ -1,9 +1,10 @@ # 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 +# those config files are stored in ./berachain//config # 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 +# if you restart the beacon node while the execution client is syncing the beacon node will crash loop until sync is done + +# delete and resync: # rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive diff --git a/berachain/reth/berachain-mainnet-reth-pruned-trace.yml b/berachain/reth/berachain-mainnet-reth-pruned-trace.yml index 16a9ad4d..8ce16776 100644 --- a/berachain/reth/berachain-mainnet-reth-pruned-trace.yml +++ b/berachain/reth/berachain-mainnet-reth-pruned-trace.yml @@ -1,9 +1,10 @@ # 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 +# those config files are stored in ./berachain//config # 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 +# if you restart the beacon node while the execution client is syncing the beacon node will crash loop until sync is done + +# delete and resync: # rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive diff --git a/bsc/bsc/bsc-chapel-bsc-pruned-pebble-path.yml b/bsc/bsc/bsc-chapel-bsc-pruned-pebble-path.yml index 08dd6972..cdc69607 100644 --- a/bsc/bsc/bsc-chapel-bsc-pruned-pebble-path.yml +++ b/bsc/bsc/bsc-chapel-bsc-pruned-pebble-path.yml @@ -13,7 +13,7 @@ services: expose: - "8545" volumes: - - bsc-chapel-bsc-pruned-pebble-path:/root/.ethereum + - bsc-chapel-bsc-pruned-pebble-path:/bsc/.ethereum - /slowdisk:/slowdisk entrypoint: [ "geth" ] command: diff --git a/bsc/bsc/bsc-mainnet-bsc-pruned-pebble-path.yml b/bsc/bsc/bsc-mainnet-bsc-pruned-pebble-path.yml index 0d2bc643..e28ead1d 100644 --- a/bsc/bsc/bsc-mainnet-bsc-pruned-pebble-path.yml +++ b/bsc/bsc/bsc-mainnet-bsc-pruned-pebble-path.yml @@ -13,7 +13,7 @@ services: expose: - "8545" volumes: - - bsc-mainnet-bsc-pruned-pebble-path:/root/.ethereum + - bsc-mainnet-bsc-pruned-pebble-path:/bsc/.ethereum - /slowdisk:/slowdisk entrypoint: [ "geth" ] command: