Closed mvandeberg closed 2 years ago
When unable to connect to a peer via gossip, the reported errors appear to increase over time:
2021-07-13 12:47:37.117350 (p2p.Koinos) [protocol/gossip.go:369] <info>: Failed to connect to gossiped peer: /ip4/*.*.*.*/tcp/64817/p2p/Qme2tpdDW1GyqNWNKGwGHQHhPBPXSiSuuLu73a3uPdAWsV, failed to dial Qme2tpdDW1GyqNWNKGwGHQHhPBPXSiSuuLu73a3uPdAWsV: * [/ip4/*.*.*.*/tcp/62111] dial backoff * [/ip4/*.*.*.*/tcp/65093] dial backoff * [/ip4/*.*.*.*/tcp/65412] dial backoff * [/ip4/*.*.*.*/tcp/64814] dial backoff * [/ip4/*.*.*.*/tcp/64941] dial backoff * [/ip4/*.*.*.*/tcp/65057] dial backoff * [/ip4/*.*.*.*/tcp/65288] dial backoff * [/ip4/*.*.*.*/tcp/64235] dial backoff * [/ip4/*.*.*.*/tcp/64666] dial backoff * [/ip4/*.*.*.*/tcp/64808] dial backoff * [/ip4/*.*.*.*/tcp/65478] dial backoff * [/ip4/*.*.*.*/tcp/64965] dial backoff * [/ip4/*.*.*.*/tcp/65442] dial backoff * [/ip4/*.*.*.*/tcp/49158] dial backoff * [/ip4/*.*.*.*/tcp/64825] dial backoff * [/ip4/*.*.*.*/tcp/64386] dial backoff ... skipping 29 errors ...
We are not seeing this on p2p in current testing. Closing in favor of a newer bug report if the behavior still exists.
When unable to connect to a peer via gossip, the reported errors appear to increase over time: