Hi, after the new update of Fuel Core to 0.31.0
I’ve encountered this weird behavior while the node is running as seen below.
Also the syncing is a bit slower as it always downloading many blocks and processing it at once instead of syncing latest block like last version.
2024-07-13T16:25:34.234808Z ERROR new{name=puckanode-sepolia-testnet}:initialize_loop{service="P2P"}: fuel_core_p2p::p2p_service: 626: RequestResponse outbound error for peer: PeerId("16Uiu2HAmDxoChB7AheKNvCVpD4PHJwuDGn8rifMBEHmEynGHvHrf") with id: OutboundRequestId(25) and error: Io(Custom { kind: Other, error: "Hit the end of buffer, expected more data" })
2024-07-13T16:25:34.234979Z ERROR fuel_core_services: 55: Failed to get headers Invalid response from peer P2P(Io(Custom { kind: Other, error: "Hit the end of buffer, expected more data" }))
2024-07-13T16:25:34.235093Z INFO new{name=puckanode-sepolia-testnet}:initialize_loop{service="ImportTask"}:import:failed_to_process{self=State { status: Processing(4975845..=4975888) } range=4975845..=4975868}: fuel_core_sync::state: 204: Status change from: Processing(4975845..=4975888), to: Committed(4975844)
2024-07-13T16:25:34.235106Z ERROR new{name=puckanode-sepolia-testnet}:initialize_loop{service="ImportTask"}: fuel_core_sync::service: 178: error=Failed to import range of blocks: 4975845..=4975868
2024-07-13T16:25:34.235113Z ERROR new{name=puckanode-sepolia-testnet}:initialize_loop{service="ImportTask"}: fuel_core_services::service: 384: e=Failed to import range of blocks: 4975845..=4975868
2024-07-13T16:25:34.336447Z INFO new{name=puckanode-sepolia-testnet}:initialize_loop{service="SyncTask"}:sync:observe{self=State { status: Committed(4975844) } height=4975889}: fuel_core_sync::state: 204: Status change from: Committed(4975844), to: Processing(4975845..=4975889)
Hey @puckapao, the slow syncing speed might be due to the SRs attacking the node and making many requests in a short time. Though, I will make sure that the team look at it and see if there’s any other issue
Yes, I’m using Ignition chainconfig since previous version and it worked fine. But after the update, it’s broken and sync every 100 blocks not real time syncing.
I wonder, what’s the usecase here if the node need to download about 100 blocks behind and playing endless catching up. I prefer previous version of fuel-core that allow real time syncing. Is there any issue with block proproser or prover? Could it be possible to open that for public to try out and reduce workload on current proposer or prover?
I will forward your question to the team, but as the last try can you try using the nightly toolchain? You might need to run the command fuelup toolchain install nightly and then run fuelup default nightly . You can also follow the guide here.
