I’ve been playing around with a private network for a while, it’s fun but I haven’t been able to get past one somewhat critical issue: The vault that starts the network is unable to rejoin (without the -f flag) if it disconnects from the network.
- I have a fairly simple config, network size set to 5 nodes, 5 VPSs running the exact same vault code/config (latest release) and everything looks about right.
- I launch one of the vaults with the -f (first) flag, I then start the other 4 nodes
- I can stop/restart the last 4 nodes in turn, they reconnect and everything seems fine
- If I ever stop/disconnect the origin node I receive errors (lost connection/no active children left) when trying to reconnect (without the -f flag)
Starting the vault back up again results in:
I 18-12-15 10:45:12.926335 Created chunk store at /tmp/safe_vault_chunk_store.iE7sPMV1f6sy with capacity of 2147483648 bytes.
I 18-12-15 10:45:13.935510 Bootstrapping(92196a…) Lost connection to proxy PublicId(name: aa3332…).
I 18-12-15 10:45:14.940915 Bootstrapping(92196a…) Lost connection to proxy PublicId(name: c93281…).
I 18-12-15 10:45:15.941582 Bootstrapping(92196a…) Lost connection to proxy PublicId(name: 8902fa…).
I 18-12-15 10:45:16.947767 Bootstrapping(92196a…) Lost connection to proxy PublicId(name: 5e076d…).
E 18-12-15 10:45:17.954003 Bootstrapper has no active children left - bootstrap has failed
I 18-12-15 10:45:17.954727 Bootstrapping(92196a…) Failed to bootstrap. Terminating.
It seems like despite having the same config, the remaining nodes refuse to allow connections from the origin node. Is there a max_children setting somewhere i haven’t seen or something else that is causing lost connections?