You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I start 3 agent nodes at the same time than 3 server node. They all have the same token set in the config.
One of the server node have no 'server' config, so it's the master of all...
So... after a while the master server is up, and the 3 agents are connected, but the 2 other servers are not connecting.
Do you mind making this more plug and play?
I think it should just work by default, then you can create an extra config if you think someone want a different behavior on startup.
Meanwhile, I try to workaround a little by having a curl wait loop in the 2 slave server, but so far, all my check are not good enough. Would you know a good curl 'test' to know that the master server is 'really' ready?
The text was updated successfully, but these errors were encountered:
This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.
Using rke2/v1.20.6+rke2r1/rke2.linux-amd64.tar.gz
I start 3 agent nodes at the same time than 3 server node. They all have the same token set in the config.
One of the server node have no 'server' config, so it's the master of all...
So... after a while the master server is up, and the 3 agents are connected, but the 2 other servers are not connecting.
Do you mind making this more plug and play?
I think it should just work by default, then you can create an extra config if you think someone want a different behavior on startup.
Meanwhile, I try to workaround a little by having a curl wait loop in the 2 slave server, but so far, all my check are not good enough. Would you know a good curl 'test' to know that the master server is 'really' ready?
The text was updated successfully, but these errors were encountered: