Skip to content
This repository has been archived by the owner on Feb 26, 2023. It is now read-only.

GUI bug and unknown allocation id #439

Closed
mnuic opened this issue Jun 14, 2019 · 11 comments
Closed

GUI bug and unknown allocation id #439

mnuic opened this issue Jun 14, 2019 · 11 comments

Comments

@mnuic
Copy link

mnuic commented Jun 14, 2019

Hi,

Today we deployed last version 1.1.0 and after that we are seeing a lot of errors like this in browser:

Unexpected response code: 500 (unknown allocation ID “XXXXXXX”)

also this:
Screenshot 2019-06-14 at 09 39 23

Consul version: 1.5.0
Nomad version: 0.8 and 0.9.1

Log:

level=error msg="connection: unable to stream /allocation/43e782e3-43b9-56de-2191-0f994917c105/stats?simple=true&interval=3s: Unexpected response code: 500 (unknown allocation ID \"43e782e3-43b9-56de-2191-0f994917c105\")" connection_id=afb69d42 source=connection
level=error msg="connection: unable to stream /allocation/c60bdbfe-ff11-96fa-e9d7-52e4ac43c965/stats?simple=true&interval=3s: Unexpected response code: 500 (unknown allocation ID \"c60bdbfe-ff11-96fa-e9d7-52e4ac43c965\")" connection_id=afb69d42 source=connection

@jippi
Copy link
Owner

jippi commented Jun 14, 2019

Unexpected response code: 500 sounds like a potential ACL issue?

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

@mnuic
Copy link
Author

mnuic commented Jun 14, 2019

We don't use ACL of any sort, that's interesting part

@hsmade
Copy link
Contributor

hsmade commented Jun 14, 2019 via email

@hsmade
Copy link
Contributor

hsmade commented Jun 18, 2019

It happens when I do a rolling restart. I see the new alloc coming online in hashi-ui, and then the error.
I'll try to get some more info

@hsmade
Copy link
Contributor

hsmade commented Jun 18, 2019

image

@hsmade
Copy link
Contributor

hsmade commented Jun 18, 2019

ALLOC_STATS is failing. I also don't get any data on /allocations//stats
This is for existing allocs. I'm not restarting or anything, just switched to the allocs page for a service.
Nomad version is 0.7.1, hashi-ui 1.0.0

@hsmade
Copy link
Contributor

hsmade commented Jun 18, 2019

I can reproduce it with hashi-ui-1.1.0

@hsmade
Copy link
Contributor

hsmade commented Jun 18, 2019

And I can't reproduce it when using nomad-0.9.3

@mnuic
Copy link
Author

mnuic commented Apr 3, 2020

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:
Get http://NomadClientIP:4646/v1/job/ServiceName?index=1337027&namespace=default&region=DcRegion&stale=&wait=120000ms: EOF

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.

@mnuic
Copy link
Author

mnuic commented May 5, 2020

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.

@mnuic
Copy link
Author

mnuic commented Oct 12, 2020

This happens because Nomad introduced limits in 0.10.3 version, explained here.

So I'm closing this one.

@mnuic mnuic closed this as completed Oct 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants