This commit is contained in:
squidbear
2025-03-29 09:24:40 +01:00
parent 1476e2032f
commit 6326cca752
6 changed files with 18 additions and 14 deletions

View File

@@ -1,9 +1,10 @@
# this is what you should know: # 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 # 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 # 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 # if you restart the beacon node while the execution client is syncing the beacon node will crash loop until sync is done
# 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 # 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 # rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive

View File

@@ -1,9 +1,10 @@
# this is what you should know: # 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 # 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 # 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 # if you restart the beacon node while the execution client is syncing the beacon node will crash loop until sync is done
# 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 # 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 # rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive

View File

@@ -1,9 +1,10 @@
# this is what you should know: # 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 # 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 # 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 # if you restart the beacon node while the execution client is syncing the beacon node will crash loop until sync is done
# 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 # 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 # rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive

View File

@@ -1,9 +1,10 @@
# this is what you should know: # 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 # 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 # 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 # if you restart the beacon node while the execution client is syncing the beacon node will crash loop until sync is done
# 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 # 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 # rm -rf berachain/mainnet/config/* && rm -rf /var/lib/docker/volumes/rpc_berachain-mainnet-reth-archive-trace*/_data/* && ./force-recreate.sh berachain-mainnet-archive

View File

@@ -13,7 +13,7 @@ services:
expose: expose:
- "8545" - "8545"
volumes: volumes:
- bsc-chapel-bsc-pruned-pebble-path:/root/.ethereum - bsc-chapel-bsc-pruned-pebble-path:/bsc/.ethereum
- /slowdisk:/slowdisk - /slowdisk:/slowdisk
entrypoint: [ "geth" ] entrypoint: [ "geth" ]
command: command:

View File

@@ -13,7 +13,7 @@ services:
expose: expose:
- "8545" - "8545"
volumes: volumes:
- bsc-mainnet-bsc-pruned-pebble-path:/root/.ethereum - bsc-mainnet-bsc-pruned-pebble-path:/bsc/.ethereum
- /slowdisk:/slowdisk - /slowdisk:/slowdisk
entrypoint: [ "geth" ] entrypoint: [ "geth" ]
command: command: