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

Keypers spam "failed to dial" error logs #467

Open
jannikluhn opened this issue Jun 28, 2024 · 1 comment
Open

Keypers spam "failed to dial" error logs #467

jannikluhn opened this issue Jun 28, 2024 · 1 comment

Comments

@jannikluhn
Copy link
Contributor

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.

@jannikluhn
Copy link
Contributor Author

downgraded the logs to DBG, but leaving the issue open due to:

We should also investigate why there's so many bad addresses in the DHT. It seems keypers advertize docker-internal addresses.

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

1 participant