-
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 UI gives errors when watching logs #5404
Comments
We have seen the same issue since upgrading to |
In our case we are behind Nginx. To fix the issue we disabled |
@robloxrob Thats a nice fix. Sadly, we run Fabio in front, so no Nginx, but it might be possible that there are some tweaks that can be applied. |
We have the same problem with Fabio 1.5.9 and Nomad 0.8.4 Maybe is related with fabiolb/fabio#324. Request:
When there are many logs (>BufferSize) everything is Ok. |
So we upgraded to Nomad 0.9.1 and the problem persists, which we expected since it is probably a Fabio thing, we haven't yet decided if we want to continue with Fabio (their newest release broke something for us that we haven't had the time to debug) or if we are switching to pure Haproxy and live without the cool Consul bindings that Fabio gives us. |
@kaspergrubbe maybe you can use this it solves our problem. What we did it's to add a Target option which adds flush to desired route. E.g: Hope that can help you |
@tommyvicananza Thank you for the workaround, that did actually solve it for us. The fix solved it for us while we migrated away from Fabio, and we have now replaced it with Haproxy and aren't seeing any issues. |
I'm experiencing the same thing, except I'm configured for TLS and on v0.9.3. I'm not fronting the Nomad UI with any proxy, I connect to directly. I see the same "Cannot fetch logs" error, except the logs will never show in the window. I'm also seeing this in the nomad server logs:
And this in the nomad UI console:
This particular task has been running for a few hours, and just now after clicking back on the Logs tab, the logs loaded properly. I'm at a loss to find any consistent behaviour :/ The "nomad alloc logs " command works all the time. When I disable TLS on the cluster, everything works in the UI. |
I also get the same error with Nomad version 0.9.3. We have put Traefik in front on Nomad, however I get this error when accessing Nomad via the load balanced address and when accessing the Web UI directly over port 4646. We also have TLS enabled on the cluster. |
I believe this issue is being resolved through [GH-5954] for the upcoming 0.9.4 release. |
I also have this issue. Load balancer: Fabio 1.5.13 This is with the Client: Firefox 85.0b8 on Ubuntu 20.04 (amd64) |
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
Operating system and Environment details
Amazon Linux 2.
Issue
When I go to an allocation and click logs nothing shows up, but after a while this shows up:
My browser console shows me this:
However, if I in the interface clicks on
Head
orTail
the logs will show up:Also,
nomad alloc logs :alloc_id
work just fine:Here is an small video of the problem:
Nomad Server logs (if appropriate)
I haven't seen anything related to these errors.
Nomad Client logs (if appropriate)
I haven't seen anything related to these errors.
The text was updated successfully, but these errors were encountered: