Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deserialization errors in P2P req_res at node startup #2371

Open
acerone85 opened this issue Oct 18, 2024 · 1 comment
Open

Deserialization errors in P2P req_res at node startup #2371

acerone85 opened this issue Oct 18, 2024 · 1 comment

Comments

@acerone85
Copy link
Contributor

Context:

I had to restart my mainnet node following it being disconnected from the network for too long, and failing to synch with relayers.
Upon restarting the node, I got the following errors related to the P2P service (here I list only the error for one peer, but there were errors for multiple peers):

2024-10-18T10:23:29.404720Z ERROR new{name=Mainnet Node}:initialize_loop{service="P2P"}: fuel_core_p2p::peer_report: 172: Dial failure: peer id `Some(PeerId("16Uiu2HAm5yqpTv1QVk3SepUYzeKXTWMuE2VqMWHq5qQLPR2Udg6s"))` with error `Dial error: dial condition was configured to only happen if there is currently no ongoing dialing attempt (`PeerCondition::NotDialing`), but a dial is in progress, thus cancelling new dial.`
2024-10-18T10:23:29.78145

[...]

2024-10-18T10:23:31.565096Z ERROR new{name=Mainnet Node}:initialize_loop{service="P2P"}: fuel_core_p2p::p2p_service: 746: RequestResponse outbound error for peer: PeerId("16Uiu2HAm5yqpTv1QVk3SepUYzeKXTWMuE2VqMWHq5qQLPR2Udg6s") with id: OutboundRequestId(54) and error: Io(Custom { kind: Other, error: "Serde Deserialization Error" })
2024-10-18T10:23:31.565173Z ERROR fuel_core_txpool::service: 551: Failed to gather tx ids from peer 16Uiu2HAm5yqpTv1QVk3SepUYzeKXTWMuE2VqMWHq5qQLPR2Udg6s: Invalid response from peer P2P(Io(Custom { kind: Other, error: "Serde Deserialization Error" }))

Also a bunch of the following errors

024-10-18T10:23:30.790438Z ERROR fuel_core_services: 70: Failed to get headers channel closed
2024-10-18T10:23:30.790111Z ERROR fuel_core_services: 70: Failed to get headers channel closed
2024-10-18T10:23:30.790488Z ERROR fuel_core_services: 70: Failed to get headers channel closed
2024-10-18T10:23:30.790492Z ERROR fuel_core_services: 70: Failed to get headers channel closed
2024-10-18T10:23:30.790501Z ERROR fuel_core_services: 70: Failed to get headers channel closed
2024-10-18T10:23:30.789762Z ERROR fuel_core_services: 70: Failed to get headers channel closed
2024-10-18T10:23:30.789900Z ERROR fuel_core_services: 70: Failed to get headers channel closed
2024-10-18T10:23:30.789964Z ERROR fuel_core_services: 70: Failed to get headers channel closed
2024-10-18T10:23:30.789854Z ERROR fuel_core_services: 70: Failed to get headers channel closed
2024-10-18T10:23:30.790464Z ERROR fuel_core_services: 70: Failed to get headers channel closed
@xgreenx
Copy link
Collaborator

xgreenx commented Oct 22, 2024

I had to restart my mainnet node following it being disconnected from the network for too long, and failing to synch with relayers.

It is strange, since you should be re-connected back again. Unless you used --bootstrap-nodes instead of --reserved-nodes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants