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

Dashboards not loading - Visualize: Failed to get the doc #2635

Closed
AlexB030 opened this issue Jan 14, 2015 · 2 comments
Closed

Dashboards not loading - Visualize: Failed to get the doc #2635

AlexB030 opened this issue Jan 14, 2015 · 2 comments

Comments

@AlexB030
Copy link

Hey together,

I am running into errors since deployment of Kibana 4 beta 3 (Build 4673, Commit SHA 8faae21).
I did not compile it myself but took the version that is already available for download from elasticsearch.org

The error occurs when I go to the "Dashboard" Tab and select one of my dashboards to be loaded.

A red bar at the upper edge appears stating the following:

"Visualize: Failed to get the doc: {"error":"SearchPhaseExecutionException[Failed to execute phase [query], all shards failed; shardFailures {[IL4Uj4lcS5ur2DFtAnYQMw][logstash-2014.11.03][0]: SearchParseException[[logstash-2014.11.03][0]: from[-1],size[-1]: Parse Failure [Failed to parse source [{"query...."

when I click on "more Info", the following is displayed:

KbnError@https://test.example.com/index.js?_b=4673:38611:21
FetchFailure@https://test.example.com/index.js?_b=4673:38661:1
fetchService/fetchThese/</</sendResponse@https://test.example.com/index.js?_b=4673:41536:62
fetchService/fetchThese/</</<@https://test.example.com/index.js?_b=4673:41545:15
fetchService/fetchThese/</<@https://test.example.com/index.js?_b=4673:41540:11
qFactory/defer/deferred.promise.then/wrappedCallback@https://test.example.com/index.js?_b=4673:20764:31
qFactory/ref/<.then/<@https://test.example.com/index.js?_b=4673:20850:26
$RootScopeProvider/this.$get</Scope.prototype.$eval@https://test.example.com/index.js?_b=4673:21893:16
$RootScopeProvider/this.$get</Scope.prototype.$digest@https://test.example.com/index.js?_b=4673:21705:15
$RootScopeProvider/this.$get</Scope.prototype.$apply@https://test.example.com/index.js?_b=4673:21997:13
done@https://test.example.com/index.js?_b=4673:17570:34
completeRequest@https://test.example.com/index.js?_b=4673:17784:7
createHttpBackend/</xhr.onreadystatechange@https://test.example.com/index.js?_b=4673:17723:1

this occurs independent from the selected time interval and amount of documents in that interval.

https is done by Squid as a reverse proxy. i also tried accessing it without Squid using plain http but I keep running into the same issue. When reverting back to beta 2 everything works fine.

The same happens when I try to create a new Dashboard... as soon as I add a visualization, this message is displayed.

Intersting thing is, that my Visualizations themselves seem to work. I can access them through the "Visualize" Tab and they work on their own.

Is this a bug or am I missing something?

In the "Discover" Tab everything is totally fine and I see my documents with all the information I expect.

I appreciate any help.

PS: My Elasticsearch version is 1.4.2 (Build hash: 927caff6f05403e936c20bf4529f144f0c89fd8c)

@rashidkpc
Copy link
Contributor

Unfortunately upgrades between betas are not supported. We expect that the object schema will be standardized after RC1 and that migrations will be supported if and when it changes. If you create a new visualization and try to add that new one to a dashboard does it work?

@AlexB030
Copy link
Author

Thank you for the quick response.
It is working now!

Just to summarize:

my existent visualization were working before, when I accesed them before through the visualization Tab. But when adding them to a newly created Dashboard it failed.

Now I created only one new Visualization (the old ones are still there), created a new Dashboard, added this new Visualization first and only THEN tried the old ones, and now the old ones work in new Dashboards again.

Sounds weird to me, but this one new visualization made my old ones work again in Dashboards.

Thanks again,
Alex

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

No branches or pull requests

2 participants