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

"nomad server-members" from a client results in 501 #1382

Closed
mitchellh opened this issue Jul 2, 2016 · 7 comments
Closed

"nomad server-members" from a client results in 501 #1382

mitchellh opened this issue Jul 2, 2016 · 7 comments
Assignees

Comments

@mitchellh
Copy link
Contributor

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:

$ nomad server-members
Error querying servers: Unexpected response code: 501 (Invalid method)

Reproduction steps

Run it on a client.

Nomad Server logs (if appropriate)

Nomad Client logs (if appropriate)

Jul  2 17:44:22 ip-10-201-101-203 nomad[1313]: http: Request /v1/agent/members, error: Invalid method

Job file (if appropriate)

@barryw
Copy link

barryw commented Jul 16, 2016

I see this on 0.4.0 as well.

@SephVelut
Copy link

SephVelut commented Aug 21, 2016

Also seeing this issue on 0.4.1. Two nomad servers and on the client server-members return 501.

@vectorhacker
Copy link

I see this on 0.4.1 running on Ubuntu 16.04 x64. Three nomad servers and the client returns 501.

@vectorhacker
Copy link

Update, nomad clients seem to take jobs just fine, they just can't report the servers they're connected to.

@yhekma
Copy link

yhekma commented Sep 2, 2016

I can confirm this also occurs on debian jessie 64 with nomad 0.4.1

@dadgar
Copy link
Contributor

dadgar commented Sep 2, 2016

Hey folks we are aware of this issue. Have not yet tackled it. Will update the issue when it is fixed

@dadgar dadgar modified the milestones: v0.5.1, 0.4.1 Sep 2, 2016
@tgross tgross modified the milestones: near-term, unscheduled Jan 9, 2020
@github-actions
Copy link

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants