Closed praetoriansentry closed 5 days ago
more logs
2024-11-13T10:51:31.785517633+08:00 [INFO] [11-13|10:51:31.785] [3/15 Batches] Downloaded blocks from datastream progress: 2829064
2024-11-13T10:51:41.785798540+08:00 [INFO] [11-13|10:51:41.785] [3/15 Batches] Downloaded blocks from datastream progress: 2985246
2024-11-13T10:51:42.796398377+08:00 [INFO] [11-13|10:51:42.796] [3/15 Batches] Saving stage progress lastBlockHeight=3000000
2024-11-13T10:51:51.785791629+08:00 [INFO] [11-13|10:51:51.785] [3/15 Batches] Downloaded blocks from datastream progress: 3000000
2024-11-13T10:51:54.383102012+08:00 [WARN] [11-13|10:51:54.382] readAllFullL2BlocksToChannel: NextFileEntry: reading file bytes: readBuffer: socket error: io.ReadFull: EOF
2024-11-13T10:51:54.385218945+08:00 [INFO] [11-13|10:51:54.384] [3/15 Batches] Finished Batches stage
2024-11-13T10:51:54.385229492+08:00 [EROR] [11-13|10:51:54.385] Error while executing stage err="[3/15 Batches] skipped block"
2024-11-13T10:51:54.385232165+08:00 [EROR] [11-13|10:51:54.385] Staged Sync err="[3/15 Batches] skipped block"
2024-11-13T10:51:54.885911327+08:00 [EROR] [11-13|10:51:54.885] Staged Sync err="mdbx_txn_begin: MDBX_TXN_OVERLAPPING: Overlapping read and write transactions for the current thread, label: chaindata, trace: [kv_mdbx.go:767 kv_mdbx.go:907 stageloop.go:215 stageloop.go:110 stageloop.go:73 asm_amd64.s:1650]"
2024-11-13T10:51:55.386878620+08:00 [EROR] [11-13|10:51:55.386] Staged Sync err="mdbx_txn_begin: MDBX_TXN_OVERLAPPING: Overlapping read and write transactions for the current thread, label: chaindata, trace: [kv_mdbx.go:767 kv_mdbx.go:907 stageloop.go:215 stageloop.go:110 stageloop.go:73 asm_amd64.s:1650]"
2024-11-13T10:51:55.887961050+08:00 [EROR] [11-13|10:51:55.887] Staged Sync err="mdbx_txn_begin: MDBX_TXN_OVERLAPPING: Overlapping read and write transactions for the current thread, label: chaindata, trace: [kv_mdbx.go:767 kv_mdbx.go:907 stageloop.go:215 stageloop.go:110 stageloop.go:73 asm_amd64.s:1650]"
It seems like there must be some related to our db read/write in the early syncing stage. We've encountered this error a few times.
The odd thing is it's not universally reproducible. In one system we were able to sync paste this stage successfully. In another system the error over and over again after doing a clean sync.