You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During normal operation, keypers show a lot of log messages similar to this:
keyper-1 | 2024/06/28 14:17:47.927391 ERR [ dht.go:96] error dialing peer error="failed to dial 12D3KooWCt78wkASE7KwtS4VenLoaPdxy9VmddzRC2UZKnRWPqEV: all dials failed\n * [/ip4/127.0.0.1/tcp/23003] dial to self attempted\n * [/ip4/172.19.0.5/tcp/23003] dial backoff" peer=12D3KooWCt78wkASE7KwtS4VenLoaPdxy9VmddzRC2UZKnRWPqEV
This should not be an error, but rather to be expected that an external address cannot be dialed. So this should be info or debug logs, ideally ones that are easily silencable.
We should also investigate why there's so many bad addresses in the DHT. It seems keypers advertize docker-internal addresses.
The text was updated successfully, but these errors were encountered:
During normal operation, keypers show a lot of log messages similar to this:
This should not be an error, but rather to be expected that an external address cannot be dialed. So this should be info or debug logs, ideally ones that are easily silencable.
We should also investigate why there's so many bad addresses in the DHT. It seems keypers advertize docker-internal addresses.
The text was updated successfully, but these errors were encountered: