Fail to load the discovery page after creating index-pattern

[monicasarbu]

Kibana version: Kibana-5.0.0-alpha5-SNAPSHOT from 25th of July

Server OS version: OSX

Browser version: Chrome

Loading the Discovery page fails after creating the metricbeat-* index-pattern in Kibana.

Steps to reproduce:

1. Start metricbeat (latest release)
2. Create a metricbeat-* index pattern in Kibana on @timestamp
3. Loading the Discovery page fails with the error below.

Errors in browser console (if relevant):

Error: [parsing_exception] Unknown key for a START_ARRAY in [stored_fields]., with { line=1 col=575 }
    at respond (http://localhost:5601/bundles/kibana.bundle.js?v=13407:22:27984)
    at checkRespForFailure (http://localhost:5601/bundles/kibana.bundle.js?v=13407:22:27212)
    at http://localhost:5601/bundles/kibana.bundle.js?v=13407:10:18968
    at processQueue (http://localhost:5601/bundles/commons.bundle.js?v=13407:38:23627)
    at http://localhost:5601/bundles/commons.bundle.js?v=13407:38:23894
    at Scope.$eval (http://localhost:5601/bundles/commons.bundle.js?v=13407:39:4619)
    at Scope.$digest (http://localhost:5601/bundles/commons.bundle.js?v=13407:39:2359)
    at Scope.$apply (http://localhost:5601/bundles/commons.bundle.js?v=13407:39:5037)
    at done (http://localhost:5601/bundles/commons.bundle.js?v=13407:37:25027)
    at completeRequest (http://localhost:5601/bundles/commons.bundle.js?v=13407:37:28702)

[jbudz]

@monicasarbu which version of elasticsearch? Kibana needs a recent build (last few weeks). I was able to import_dashboards.sh from that PR (although with metricbeat-alpha4 data)

[monicasarbu]

@jbudz I am using Elasticsearch alpha4. Importing the dashboards (using the import_dashboards.sh) works just fine, but when you open the Discovery page, the error is raised. I will try with a newer version of Elasticsearch.

[monicasarbu]

It seems to work with the latest Elasticsearch version, so closing the issue. Thank you @jbudz for your help.

[gprabhu-repos]

I ran into this error too. What is the underlying issue here?

[jbudz]

A breaking change in elasticsearch and a subsequent patch in kibana. If you're running snapshot builds I would make sure to grab the latest of both. Keep in mind this shouldn't be happening on full releases as long as the versions match.

[gprabhu-repos]

I already have installed latest version available at https://www.elastic.co/downloads/elasticsearch (5.0.0-alpha4). Are you suggesting I clone master from https://github.com/elastic/elasticsearch and build from source? Are there build/ install instructions for that?

[jbudz]

Only suggesting doing that if you're running a kibana snapshot or master (vs the alpha 4 download here. If you're running elasticsearch alpha 4 and kibana alpha 4 then this sounds like a (different) legitimate bug.

Regarding building from source, yeah that would work. Detailed instructions can be found at https://github.com/elastic/elasticsearch/blob/master/CONTRIBUTING.md#contributing-to-the-elasticsearch-codebase, the short version being cloning and running gradle assemble. I do a combination of that and using https://www.npmjs.com/package/esvm (which tends to run a few weeks behind) for development.

[frithz]

I too have experienced this problem after updating my ELK stack to 5.0.0-alpha5.
[(https://discuss.elastic.co/t/kibana-parsing-exception-on-unknown-key-for-a-start-array/59574)]

[ghost]

Hello, I am still experiencing this exact issue with RC1. Does anyone have any ideas?

[monicasarbu]

@schn0052 are you using RC1 versions for Elasticsearch and Kibana?

[johnny1952]

@monicasarbu
hi, I have got the this problem with rc1.

[monicasarbu]

@johnny1952 Are you running both Elasticsearch and Kibana of the same version (rc1)? Did you upgrade from 5.0.0-alphaX to 5.0.0-rc1, or from 1.x? For me, it seems to work with 5.0.0-alpha5, and also when upgrading from 5.0.0-alpha4 to 5.0.0-rc1.

[johnny1952]

@monicasarbu
The version of elasticsearch is 5.0.0-alpha4, and kibana's version is 5.0.0-rc1.
Thanks.

[monicasarbu]

@johnny1952 Indeed. I am able to reproduce the issue when using Metricbeat 5.0.0-alpha4, Elasticsearch 5.0.0-alpha4 and Kibana 5.0.0, but it disappears when upgrading Elasticsearch to 5.0.0-alpha5. Now, that 5.0.0 is out, an option would be to upgrade Elasticsearch directly to 5.0.0. I hope this helps.