Skip to content

Socket (P2P) instability while syncing #198

@davidtavarez

Description

@davidtavarez

After testing PR #196 I can notice that there is some instability on Grin++ nodes. I'm using the next list known Grin++ nodes:

[
	"217.160.242.228",
	"217.160.66.118",
	"212.227.210.43",
	"93.90.194.26",
	"82.165.107.169",
	"107.174.63.210",
	"grinpp01.grinnode.live",
	"grinpp02.grinnode.live",
	"grinpp03.grinnode.live"
]

All of the above nodes are Grin++ public nodes except for one: 107.174.63.210. Although the node manages to connect to the peers, the Grin++ fails to maintain a stable connection to each of them.

Screenshot 2022-02-16 214022

After few seconds only the MW/Grin 5.1.1 remain relatively stable.
Screenshot 2022-02-16 214359

The next are examples of the logs messages:

Disconnecting from socket 142.132.167.15:3414. Error: The I/O operation has been aborted because of either a thread exit or an application request.
Disconnecting from socket 82.165.107.169:3414. Error: End of file
Disconnecting from socket 107.174.63.210:3414. Error: An operation was attempted on something that is not a socket.
Disconnecting from socket 142.132.168.230:3414. Error: <none>

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions