Beta unable to resume Sync if stopped #7039
Comments
argakiig
added
C-bug
|
oh I think I may know why this would be the case, I was using the existing docker-compose stack in ./etc, and it mounts the db as a volume but doesnt include blobstore or static_files interestingly enough though the following diff when applied causes reth to crash index 7323163c..3ef4694c 100644
--- a/etc/docker-compose.yml
+++ b/etc/docker-compose.yml
@@ -11,8 +11,12 @@ services:
- '8545:8545' # rpc
- '8551:8551' # engine
volumes:
- - rethdata_mainnet:/root/.local/share/reth/mainnet/db
- - rethdata_sepolia:/root/.local/share/reth/sepolia/db
+ - rethdata_mainnet_db:/root/.local/share/reth/mainnet/db
+ - rethdata_mainnet_blobstore:/root/.local/share/reth/mainnet/blobstore
+ - rethdata_mainnet_static_files:/root/.local/share/reth/mainnet/static_files
+ - rethdata_sepolia_db:/root/.local/share/reth/sepolia/db
+ - rethdata_sepolia_blobstore:/root/.local/share/reth/sepolia/blobstore
+ - rethdata_sepolia_static_files:/root/.local/share/reth/sepolia/static_files
- rethlogs:/root/rethlogs
- ./jwttoken:/root/jwt:ro
# For Sepolia, replace `--chain mainnet` with `--chain sepolia`
@@ -64,9 +68,17 @@ services:
/run.sh"
volumes:
- rethdata_mainnet:
+ rethdata_mainnet_db:
driver: local
- rethdata_sepolia:
+ rethdata_mainnet_blobstore:
+ driver: local
+ rethdata_mainnet_static_files:
+ driver: local
+ rethdata_sepolia_db:
+ driver: local
+ rethdata_sepolia_blobstore:
+ driver: local
+ rethdata_sepolia_static_files:
driver: local
rethlogs:
driver: localwith the following error |
also works fine |
|
Thanks! @joshieDo @shekhirin |
|
@argakiig can you also share the CL logs? I don't see any forkchoice updates in Reth logs, and we can't start the sync without at least one. So I think there may be an issue with CL not sending updates. |
|
It's currently a day and a half into the latest sync, I don't wanna try and repro currently, using l |
|
updated to the latest v0.2.0-beta1 tag at |
Describe the bug
When starting a sync attempt with the new db specifically the 0.2.0-beta.1 tag everything works fine
Logs are as expeccted
but after stopping the node and starting it back up again it is unable to connect to prysm and prysm is unable to connect to it.
the logs change as follows
I am able to get the db to start syncing again if i blow the db away
Steps to reproduce
Start reth and your choice of consensus engine
let it begin syncing
stop the node and let it gracefully shutdown,
restart reth observe it stops progressing
Node logs
Platform(s)
Linux (x86)
What version/commit are you on?
reth Version: 0.2.0-beta.1 Commit SHA: aec59b7 Build Timestamp: 2024-03-07T17:10:28.313032547Z Build Features: jemalloc Build Profile: maxperf
What database version are you on?
reth db version
Current database version: 2
Local database version: 2
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
docker build . -t local-reth-beta --build-arg BUILD_PROFILE=maxperf --build-arg FEATURES=jemalloc,asm-keccak
Code of Conduct
The text was updated successfully, but these errors were encountered: