-
Notifications
You must be signed in to change notification settings - Fork 149
GUI bug and unknown allocation id #439
Comments
I don't have a 0.9 Nomad cluster to test on atm, but 1.1.0 works fine for a 0.8.7 cluster |
We don't use ACL of any sort, that's interesting part |
Getting the same thing here, after upgrading.
…On Fri, Jun 14, 2019 at 11:44 AM mnuic ***@***.***> wrote:
We don't use ACL of any sort, that's interesting part
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#439?email_source=notifications&email_token=AAIVN5IAHMAWXXL5HWDI5LLP2NSALA5CNFSM4HYFMAE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXWJTGY#issuecomment-502045083>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIVN5L3AAQ7ALX4VZZPXJLP2NSALANCNFSM4HYFMAEQ>
.
|
It happens when I do a rolling restart. I see the new alloc coming online in hashi-ui, and then the error. |
ALLOC_STATS is failing. I also don't get any data on /allocations//stats |
I can reproduce it with hashi-ui-1.1.0 |
And I can't reproduce it when using nomad-0.9.3 |
just installed nomad 0.10.5, hashi_ui 1.3.4 and this still happens randomly. We are using haproxy but even when I hit the container IP addr and port for hashi_ui it's the same: tried the last version 1.3.8, but no luck. When I try manually to trigger the GET link in browser I always get response. |
This is starting to be pain in the ... even without the proxy, when manually connecting to hashi_ui container above error happens. We are using Consul v1.7.2 and Nomad v0.10.5. |
This happens because Nomad introduced limits in 0.10.3 version, explained here. So I'm closing this one. |
Hi,
Today we deployed last version 1.1.0 and after that we are seeing a lot of errors like this in browser:
also this:
Consul version: 1.5.0
Nomad version: 0.8 and 0.9.1
Log:
The text was updated successfully, but these errors were encountered: