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

ConnectionSupervisor does not handle restart properly #1419

Open
bchamagne opened this issue Feb 6, 2024 · 0 comments
Open

ConnectionSupervisor does not handle restart properly #1419

bchamagne opened this issue Feb 6, 2024 · 0 comments
Labels
bug Something isn't working P2P Involve P2P networking

Comments

@bchamagne
Copy link
Member

bchamagne commented Feb 6, 2024

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

@bchamagne bchamagne added bug Something isn't working P2P Involve P2P networking labels Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P2P Involve P2P networking
Projects
None yet
Development

No branches or pull requests

1 participant