Timelion Page Blank after update

[pawprint-net]

Kibana version:
5.2.2

Elasticsearch version:
5.2.2

Server OS version:
CentOS 7

Browser version:
Chrome + Firefox + IE + Safari (several versions)

Browser OS version:
Windows, Mac, Linux

Original install method (e.g. download page, yum, from source, etc.):
source (v4)

Description of the problem including expected versus actual behavior:
The timelion page is blank (with the exception of the left side nav) - all other modules and components of Kibana work fine.

Steps to reproduce:

1. Install ELK Stack v4
2. Upgrade to current version
3. Navigate to Timelion page in web UI

Errors in browser console (if relevant):
none

Provide logs and/or server output (if relevant):

This is a duplicate of Issue number 12 in the old timelion issue tracker. That was never resolved and people are still commenting on the closed issue looking for some help.

The issue there seems to be the problem but none of the proposed fixes work with the 5.2 version so the primary question remains:

For someone stuck in this situation on the 5.2.x release - how does one fix it?

[weltenwort]

I was unable to reproduce this when upgrading from Elasticsearch 2.4.4 + Kibana 4.6.4 to the Elastic Stack 5.2.1. A timelion sheet created on 4.6.4 could be loaded on 5.2.1 without errors.

This supports the claim that this problem was fixed in #4509. Older indices might still be broken, of course, and require reindexing with a fixed mapping as described in the comments of elastic/timelion#12.

Can you provide more detailed instructions that could help to reproduce this?

[pawprint-net]

I finally got it to work - needed to modify the code that was provided in the other issue slightly so for anyone else needing a working snippit assuming localhost:

curl -XPOST 'localhost:9200/_reindex?pretty' -d'
{
  "source": {
    "index": ".kibana"
  },
  "dest": {
    "index": ".kibana1"
  },
  "script": {
    "inline": "ctx._source.remove(\"version\")"
  }
}
'
curl -XPOST 'localhost:9200/_reindex?pretty' -d'
{
  "source": {
    "index": ".kibana1"
  },
  "dest": {
    "index": ".kibana2"
  },
  "script": {
    "inline": "ctx._source.remove(\"hits\")"
  }
}
'

[jbudz]

Thanks for posting the fix @sbaker-gsc. This is the same as #9888, it occurs when sections of the kibana index are created before mappings are set. We are working on defining mappings earlier.