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

public environment node restart #464

Open
ivcosla opened this issue Jul 2, 2019 · 0 comments
Open

public environment node restart #464

ivcosla opened this issue Jul 2, 2019 · 0 comments

Comments

@ivcosla
Copy link

ivcosla commented Jul 2, 2019

When using the public environment, if you start new nodes the environment works well, they are able to stablish transports and routes and make the apps work.

However, when nodes are restarted:

  1. Each node re-stablish the previous transports, and they are reported as such by the cli
  2. If you try to use an app, route-finder will report that there is no route available between the nodes, however the transports are there
  3. If you try to re-stablish the old transports manually (skywire-cli --rpc $RPC_A node add-tp $PK_B for example) it will timeout during handshake, as opposed to what happens with fresh nodes
  4. You can manually remove the old transports and add new ones, the result is the same as in 3)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant