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

Install a Nomad cluster with Consul on cloud servers #1002

Closed
gselva opened this issue Nov 20, 2024 · 2 comments · Fixed by #1049
Closed

Install a Nomad cluster with Consul on cloud servers #1002

gselva opened this issue Nov 20, 2024 · 2 comments · Fixed by #1049

Comments

@gselva
Copy link

gselva commented Nov 20, 2024

Problem

This line is a bit confusing retry_join should contain at least one of your servers internal IP adresses as it is not clear which "servers" is meant.

Suggested Fix

The line would be clearer like this:
retry_join should contain at least one of your other servers internal IP adresses (do not use the internal IP of the server where you are updating this setting)

@sahina
Copy link

sahina commented Jan 6, 2025

is this incorrect? retry_join = ["10.0.0.2", "10.0.0.3", "10.0.0.4"]

@svenja11
Copy link
Collaborator

@gselva Thank you for your feedback!




@sahina This depends on the server you're on. If you have three servers with the IPs 10.0.0.2, 10.0.0.3 and 10.0.0.4, it would look like this:

[email protected]~$ nano /etc/systemd/system/nomad.service
retry_join = ["10.0.0.3", "10.0.0.4"]
[email protected]~$ nano /etc/systemd/system/nomad.service
retry_join = ["10.0.0.2", "10.0.0.4"]
[email protected]~$ nano /etc/systemd/system/nomad.service
retry_join = ["10.0.0.2", "10.0.0.3"]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants