Skip to content
This repository was archived by the owner on Jan 7, 2022. It is now read-only.
This repository was archived by the owner on Jan 7, 2022. It is now read-only.

Spotted in logs: a lot of attempts to connect to onion addresses that fail. Tor at 100% cpu #827

@kowalski

Description

@kowalski

I have plenty of messages like:

May 14 18:04:27.000 [notice] Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.

Something in libp2p makes a lot of connections. Maybe it's our network "rembering" old peers that are now gone. It may be that our entry node has a big libp2p.addressBook with plenty of these addresses and it's telling new clients to connect to them.

If this is a case, we should see how to make that the failure of connection in WebSocketOverTor translates to removing the address from addressBook, so that our network doesn't accumulate garbage.

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