-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Nomad worker failed to start running after upgrading to 0.9.2 #5795
Comments
Looks like Nomad 0.9.2 is trying to connect to consul with HTTP instead of HTTPS, even though my Consul config for Nomad is this:
|
@xbglowx Thanks for reaching out. I just succeeded in setting up a nomad client with a consul configured with TLS, and looks like we may need a deeper look. Can you try the following steps and provide more information please:
|
@xbglowx Could you provide your nomad agent's config in its entirety here? Will aid us in debugging further |
Yes, I will do that today. |
Here is the entire client config:
Nomad is started as so:
After changing consul address to 127.0.0.1:8501 and restarting Nomad, I don't get anything new in the logs. Below is showing the current timestamp, last Nomad log entry, and process table entry:
This is how other Nomad workers see this node:
I don't see
|
Thank you so much for reporting this issue. This was fixed by #5817. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Nomad v0.9.2 (028326684b9da489e0371247a223ef3ae4755d87)
Operating system and Environment details
Issue
Upgrading from Nomad 0.9.1 to 0.9.2 causes client.consul errors and failure to rejoin the cluster. Rolling back to 0.9.1 fixes the problem.
Reproduction steps
Job file (if appropriate)
Nomad Client logs (if appropriate)
Nomad Server logs (if appropriate)
The text was updated successfully, but these errors were encountered: