Skip to content

ConnectionSupervisor does not handle restart properly #1419

Open

Description

Describe the problem you discovered

We had an issue where the module Connection was being terminated very quickly due to an issue with libsodium.
This resulted in a "reached max restart intensity" of the ConnectionSupervisor.
The ConnectionSupervisor was restarted with an empty state, which means no Connection.

Capture d’écran 2024-02-06 à 10 14 33
(screenshot of the network view of the incriminating node)

I used Archethic.P2P.connect_nodes(Archethic.P2P.MemTable.available_nodes) to restart the connections.

Describe the solution you'd like

Somehow, if the ConnectionSupervisor is restarted, we need to reconnect to the nodes

Epic

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    P2PInvolve P2P networkingbugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions