Skip to content
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

Silently failure when ElasticSearch is unreachable #76

Closed
To-om opened this issue Apr 3, 2018 · 1 comment
Closed

Silently failure when ElasticSearch is unreachable #76

To-om opened this issue Apr 3, 2018 · 1 comment
Assignees
Labels
Milestone

Comments

@To-om
Copy link
Contributor

To-om commented Apr 3, 2018

Request Type

Bug

Work Environment

Cortex 2.0.1

Problem Description

If ElasticSearch is not started, Cortex web interface shows an empty page, without any error message.

Complementary information

If ElasticSearch is unreachable, Cortex back-end returns the following error on any requests that need ES:

500 Internal Server Error

{"type":"NoNodeAvailable","message":"ElasticSearch cluster is unreachable"}
@To-om To-om added this to the 2.0.2 milestone Apr 3, 2018
@nadouani nadouani added the bug label Apr 3, 2018
@nadouani nadouani closed this as completed Apr 3, 2018
nadouani added a commit that referenced this issue Apr 3, 2018
@liuxuehao
Copy link

Now I have the same problem, when I pull the image in docker and run it. Access it via google browser, prompting ‘’Error: ElasticSearch cluster is unreachable ’’
Ubuntu 16.04.3
Docker 19.03.1
Cortex: 3.0.0-RC4
Elasticsearch: 6.8.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants