-
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 monitor
always panics
#6827
Comments
I decided to re-check if this part is accurate. If called without arguments at all, |
It appears that this happens when there are no nodes found for the provided #6828 should fix the problem. |
I've filled #6845 as a follow up for Server node support. Sorry about that, it's confusing in our docs. |
@m1kc - Oops, I missed that we have a |
Thanks for pointing that out! And... well, it looks like I still can't get it to work with server node. So, it still works fine without arguments, streaming logs from current node, it works with
It's the same id you see on the screenshot above. I double-checked that it's actually a server id (and not a client id), it's actually valid, the server did not change its id for some reason, I'm pointing at the right machine and it actually has Nomad v0.10.2 (0d2d6e3) installed. I can't actually try that with another 0.10.x server (for now, 'cause the other ones are still on 0.9.x), so can't say if the problem is only with this one. But, just for the sake of experiment, I tried requesting logs from these 0.9 servers anyway, and it returns exactly the same error message with code 400. Here are these responses too, in case I'm missing something again:
Now, as you could probably tell, I still feel kinda stupid after missing that |
Hi @m1kc sorry for the confusion. Currently the Based off of your screen shot the following should work
|
That was... unexpected. But it worked, thanks! |
I agree it's confusing and will be fixed in #6847. Sorry for the inconvenience, glad to hear its working now. |
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.10.2 (0d2d6e3)
Operating system and Environment details
Issue
nomad monitor
always fails with the following output, no matter what log-level and node-id I use:Some nodes in the cluster are still on 0.9, but I don't try to get logs from them.
Reproduction steps
Call
nomad monitor
with any arguments.Job file (if appropriate)
Nomad Client logs (if appropriate)
Nomad Server logs (if appropriate)
No new log lines appear after that command.
The text was updated successfully, but these errors were encountered: