Unable to Read Node List!

[espogian]

Hello, opening ElasticHQ dashboard the "Unable to Read Node List!" error message is shown on top of the page.

The rest of the information is displayed properly.

I can't understand why this error is showing, and how to investigate.

Could someone share some ideas? :)

[sundar reddy]

Even I'm facing same issue. Is any luck to fix this issue?

[Camilo G]

I am facing the same problem.
the status says "yellow"
my console  says: " Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[tooblerc][2]]"
I cannot use the Query feature either but I can see the index name and all the fields "checked"

[Abhinav D]

Using master branch will solve this issue if you are using Elasticsearch 5.x and above

source: https://github.com/royrusso/elasticsearch-HQ/issues/278

On Friday, February 17, 2017 at 12:56:45 PM UTC-6, Hurturk Yagmur wrote:

That might be due ElasticHQ not being completely ready for 5. If you go to debugger, you will see it attempts to call ?all=true instead of _all to retrieve nodes.

You can fix a little but there are many other issues may raise for other reasons. See xbgmsharp's answers at:

see: https://github.com/royrusso/elasticsearch-HQ/issues/267

Example fix for mac users:

sed -ie 's/nodes?all=true/nodes\/_all/g' js/all.min.js

Yellow status is because there are no replicas, safe to ignore for development I suppose.