cannot connect to peer

[garyng2000]

Describe the bug

I have a private(interop) setup that works generally. But at times, a beacon chain refuses to connect to the defined peers(it worked as it can do the init sync). the log message is just

failed to negotiate security protocol: read tcp4 172.16.0.64:43000->172.16.0.72:33000: wsarecv: An existing connection was forcibly closed by the remote host. peer=16Uiu2HAkyHmP9C8G3k5LxNd1B8pYSxHfcuzbG8sFJwVmdL8oiZQF

or

failed to negotiate security protocol: EOF peer=16Uiu2HAkyHmP9C8G3k5LxNd1B8pYSxHfcuzbG8sFJwVmdL8oiZQF

this happens in both windows version as well as linux(amd64).

and once this happens, it cannot dial that node anymore

Has this worked before in a previous version?

not sure, it works randomly

🔬 Minimal Reproduction

No response

Error

No response

Platform(s)

No response

What version of Prysm are you running? (Which release)

No response

Anything else relevant (validator index / public key)?

No response

[garyng2000]

if I delete the p2p info(metadata and key), it seems to work again

[prestonvanloon]

Can you share reproduction steps?

[LovelyGuy18]

@garyng2000 , I have the same issue.
Could you tell me how to delete the p2p info(metadata and key), please?

[syjn99]

@garyng2000
It may be placed into your data directory. (network-keys & metaData) Deleting p2p info will reset your identity in p2p network.

[artjoma]

prysm 5.1.0

time="2024-09-29 14:47:16" level=error msg="failed to reconnect to peer" addrs=[/ip4/*.*.*.213/tcp/13000] error="failed to dial: failed to dial 16Uiu2HAmJh4JEk7BTQ9LAqWssbN4YAxFrLV6T9xkYKBHZ72UPFjf: all dials failed
  * [/ip4/*.*.*.213/tcp/13000] failed to negotiate security protocol: EOF" peer=16Uiu2HAmJh4JEk7BTQ9LAqWssbN4YAxFrLV6T9xkYKBHZ72UPFjf prefix=p2p
time="2024-09-29 14:47:21" level=info msg="Waiting for enough suitable peers before syncing" prefix=initial-sync required=1 suitable=0
time="2024-09-29 14:47:21" level=error msg="failed to reconnect to peer" addrs=[/ip4/*.*.*.213/tcp/13000] error="failed to dial: failed to dial 16Uiu2HAmJh4JEk7BTQ9LAqWssbN4YAxFrLV6T9xkYKBHZ72UPFjf: all dials failed
  * [/ip4/*.*.*.213/tcp/13000] dial backoff" peer=16Uiu2HAmJh4JEk7BTQ9LAqWssbN4YAxFrLV6T9xkYKBHZ72UPFjf prefix=p2p
time="2024-09-29 14:47:26" level=info msg="Waiting for enough suitable peers before syncing" prefix=initial-sync required=1 suitable=0
time="2024-09-29 14:47:31" level=info msg="Waiting for enough suitable peers before syncing" prefix=initial-sync required=1 suitable=0

[artjoma]

Can you share reproduction steps?

• setup private chain geth+beacon+validator on machine A
• after 10-12h setup node geth+beacon(using --peer) on machine B
• beacon on machine B will try download data from beacon A but after ~1h of sync. process stop wih "failed to dial" err.

[pleerock]

@artjoma I do not use prysm, but I do use libp2p (dep of prysm, which is the error original comes from). Did you always have this issue? Or does it happen after prysm upgrade?

[artjoma]

Did you always have this issue?
Yes, with 5.1.0 and 5.0.x versions. It's reproduced every time.

Exists similar issue: #14427