-
Notifications
You must be signed in to change notification settings - Fork 2k
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 server-members" from a client results in 501 #1382
Comments
I see this on 0.4.0 as well. |
Also seeing this issue on 0.4.1. Two nomad servers and on the client |
I see this on 0.4.1 running on Ubuntu 16.04 x64. Three nomad servers and the client returns 501. |
Update, nomad clients seem to take jobs just fine, they just can't report the servers they're connected to. |
I can confirm this also occurs on debian jessie 64 with nomad 0.4.1 |
Hey folks we are aware of this issue. Have not yet tackled it. Will update the issue when it is fixed |
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
0.3.2
Operating system and Environment details
Ubuntu 14.04
Issue
When I run
nomad server-members
on a server its fine, but when I run it on a client I get the output below:Reproduction steps
Run it on a client.
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: