Can't sync execution client
Closed this issue · 1 comments
yabirgb commented
Describe the bug
The execution client shows
execution-client | 2023-01-28 11:49:18.8819|Waiting for peers... 58s
execution-client | 2023-01-28 11:49:19.8805|Waiting for peers... 59s
execution-client | 2023-01-28 11:49:20.5728|Request starting HTTP/1.1 POST http://execution:8552/ application/json 1972
execution-client | 2023-01-28 11:49:20.5728|Received a new payload: 26190518 (0x7c64b79c530b37428ff25ef577d4c8a867ce9bc9ff18c0d0234e3b56e1f65a21)
execution-client | 2023-01-28 11:49:20.5728|Syncing... Parent wasn't processed. Inserting block 26190518 (0x7c64b7...f65a21).
execution-client | 2023-01-28 11:49:20.5728|Request finished HTTP/1.1 POST http://execution:8552/ application/json 1972 - 200 - application/json 1.0603ms
execution-client | 2023-01-28 11:49:20.5728|Request starting HTTP/1.1 POST http://execution:8552/ application/json 59
execution-client | 2023-01-28 11:49:20.5728|Executing JSON RPC call eth_syncing with params []
execution-client | 2023-01-28 11:49:20.5728|Request finished HTTP/1.1 POST http://execution:8552/ application/json 59 - 200 - application/json 0.2847ms
execution-client | 2023-01-28 11:49:20.5942|Request starting HTTP/1.1 POST http://execution:8552/ application/json 340
execution-client | 2023-01-28 11:49:20.5942|Received: ForkchoiceState: (HeadBlockHash: 0x7c64b79c530b37428ff25ef577d4c8a867ce9bc9ff18c0d0234e3b56e1f65a21, SafeBlockHash: 0xa1a17b8bec26f83dad79afbd286884ffdd4e06624bd734cfdcb195fbb988855d, FinalizedBlockHash: 0xafbce30e2ef4af18451b65ad3b565d2affb807dd4cc6d7a12c38f7baa9b09390)
execution-client | 2023-01-28 11:49:20.5942|Syncing beacon headers... Request: ForkchoiceState: (HeadBlockHash: 0x7c64b79c530b37428ff25ef577d4c8a867ce9bc9ff18c0d0234e3b56e1f65a21, SafeBlockHash: 0xa1a17b8bec26f83dad79afbd286884ffdd4e06624bd734cfdcb195fbb988855d, FinalizedBlockHash: 0xafbce30e2ef4af18451b65ad3b565d2affb807dd4cc6d7a12c38f7baa9b09390) .
execution-client | 2023-01-28 11:49:20.5942|Request finished HTTP/1.1 POST http://execution:8552/ application/json 340 - 200 - application/json 0.7190ms
execution-client | 2023-01-28 11:49:20.5942|Request starting HTTP/1.1 POST http://execution:8552/ application/json 59
execution-client | 2023-01-28 11:49:20.5942|Executing JSON RPC call eth_syncing with params []
execution-client | 2023-01-28 11:49:20.5942|Request finished HTTP/1.1 POST http://execution:8552/ application/json 59 - 200 - application/json 0.4291ms
execution-client | 2023-01-28 11:49:20.8820|Waiting for peers... 0s
execution-client | 2023-01-28 11:49:21.8821|Peers | with known best block: 0 | all: 0 |
execution-client | 2023-01-28 11:49:21.8821|Waiting for peers... 1s
execution-client | 2023-01-28 11:49:22.8806|Waiting for peers... 2s
and it has not synced in a few days. The execution_data folder is around 200MB
To Reproduce
I have the following env configuration
# --- Global configuration ---
EL_NETWORK=xdai
CL_NETWORK=gnosis
# --- Execution Layer - Execution Node - configuration ---
EC_IMAGE_VERSION=nethermind/nethermind:1.14.7
NETHERMIND_LOG_LEVEL=INFO
EC_ENABLED_MODULES=[Web3,Eth,Subscribe,Net,]
EC_NODENAME=Nethermind
NETHERMIND_METRICS_PUSH_GATEWAY_URL=http://localhost:9090/metrics
NETHERMIND_PRUNING_CACHEMB=2048
EC_DATA_DIR=./execution-data
EC_SNAP_SYNC_ENABLED=true
EC_JWT_SECRET_PATH=/media/vault/siedge/jwtsecret
# --- Consensus Layer - Beacon Node - configuration ---
CC_PEER_COUNT=50
CC_LOG_LEVEL=info
EC_API_URL=http://execution:8546
EC_AUTH_URL=http://execution:8552
CC_INSTANCE_NAME=Lighthouse
CC_IMAGE_VERSION=sigp/lighthouse:v3.3.0
CC_DATA_DIR=./consensus-data
CC_JWT_SECRET_PATH=/media/vault/siedge/jwtsecret
CL_FEE_RECIPIENT=REDACTED
CHECKPOINT_SYNC_URL=https://checkpoint.gnosischain.com
CL_BOOTNODES="REDACTED"
# --- Consensus Layer - Validator Node - configuration ---
CC_API_URL=http://consensus:4000
GRAFFITI=nethermind-lighthouse
VL_LOG_LEVEL=info
VL_INSTANCE_NAME=LighthouseValidator
VL_IMAGE_VERSION=sigp/lighthouse:v3.3.0
KEYSTORE_DIR=./keystore
VL_DATA_DIR=./validator-data
yabirgb commented
In case anyone needs it for me it was that the bootnodes were not configured by default and it was failing to connect to any node https://docs.gnosischain.com/updates/2022/12/08/temporary-bootnodes/