After installation on Kibana 4.2.0 the page is blank #12
Comments
|
This was a Kibana bug that was fixed here: elastic/kibana#4509 |
|
Experiencing the same issue in 4.2.1. Was it meant to be fixed? Or is there a manual action I need to perform? |
|
Ended up having to run the following: Looks like for some reason my .kibana index (likely as it's been upgraded all the way from early v4 betas) has the "version" mapping as "long". Once I modified the timelion-sheet PUT request and performed it manually as above it now loads. Thought not sure how to actually fix the mapping... Spent an hour trying to work out a way to create new .kibana index and copy things over but can't quite get anything to copy the documents and would rather avoid scripting something myself. Tried elasticsearch-exporter but it detects zero documents. |
|
Also on Kibana 4.2.0, also having blank page but a different error it seems TypeError: Cannot read property 'value' of undefined |
|
I've the same problem
I've configured a reverse proxy on apache <Location /bundles> <Location /app/kibana> |
|
I'm getting the same problem on I seem to have fixed it by running: curl -XPUT http://localhost:9200/.kibana/_mapping/dashboard -d '{
"dashboard":{
"properties":{
"title":{
"type":"string"
},
"hits":{
"type":"integer"
},
"description":{
"type":"string"
},
"panelsJSON":{
"type":"string"
},
"optionsJSON":{
"type":"string"
},
"uiStateJSON":{
"type":"string"
},
"version":{
"type":"long"
},
"timeRestore":{
"type":"boolean"
},
"timeTo":{
"type":"string"
},
"timeFrom":{
"type":"string"
},
"kibanaSavedObjectMeta":{
"properties":{
"searchSourceJSON":{
"type":"string"
}
}
}
}
}
}' |
|
Fix for kibana 4.3.0: |
|
Confirmed; the above fix by @vlad-aleksandrov corrected the issue in my install. |
|
same here in kibana 4.5 :-/ fixed by: "curl -XPUT http://IP:9200/.kibana/_mapping/timelion-sheet -d '{"timelion-sheet":{"properties":{"title":{"type":"string"},"hits":{"type":"integer"},"description":{"type":"string"},"timelion_sheet":{"type":"string"},"timelion_interval":{"type":"string"},"timelion_other_interval":{"type":"string"},"timelion_chart_height":{"type":"integer"},"timelion_columns":{"type":"integer"},"timelion_rows":{"type":"integer"},"version":{"type":"long"},"kibanaSavedObjectMeta":{"properties":{"searchSourceJSON":{"type":"string"}}}}}}'" |
|
Putting the mapping worked for me as well but I had to use the Kibana details:
|
|
For 4.5.1 use "curl -XPUT http://IP:9200/.kibana/_mapping/timelion-sheet -d '{"timelion-sheet":{"properties":{"title":{"type":"string"},"hits":{"type":"long"},"description":{"type":"string"},"timelion_sheet":{"type":"string"},"timelion_interval":{"type":"string"},"timelion_other_interval":{"type":"string"},"timelion_chart_height":{"type":"integer"},"timelion_columns":{"type":"integer"},"timelion_rows":{"type":"integer"},"version":{"type":"long"},"kibanaSavedObjectMeta":{"properties":{"searchSourceJSON":{"type":"string"}}}}}}'" |
|
Why this issue is closed? I have the same issue with the version 4.5.1 |
|
This issue still persists in 4.6.0. Because of this, timelion is literally useless with my current Elasticsearch cluster |
|
+1 this is still an issue |
|
Happens to me with latest Kibana 5.0.0 too. |
|
@kasabov on 5.0.0 you don't need to install timelion any more as its part of the core plugins. |
|
@ppisljar you're right, timelion was installed by default with the latest Kibana 5.0.0. However, navigating to the timelion page shows a blank page due to the faulty mappings discussed on this page. |
|
Happens to me with latest Kibana 5.0.1 too. elasticsearch log |
|
Same here with Kibana 5.1.1 |
|
can confirm that I've it the same. |
|
Is there a work around for this? |
|
@maniankara could you please provide some more details:
|
|
In my case, I upgraded from Elasticsearch 2.4.1 and didn't install timelion plugin. |
|
@rashidkpc what would be the right way to address this in your opinion ? |
|
There's probably not much we can do, this can happen if someone imports saved objects into Kibana without using Kibana's built in importer. If at any time someone allows a document with a The problem isn't so much timelion as it is having a The right way to prevent this would be to turn off dynamic mapping in the |
|
@rashidkpc is there something users could do once they are in this situation to get out of it ? |
|
To bump and amplify what @ppisljar requested - if there is some advice for users stuck with a blank timelion page in 5.1.2 it would be great to know. All the suggested 4.x mapping fixes above error-out in the 5.x versions (at least they do for me) |
|
Although I upgrade to 5.2.0, this problem was not resolved. |
|
I create index .kibana with { "index.mapper.dynamic": false } but then it doesn't work beacuse I get this error when I start Kibana: [type_missing_exception] type[config] missing, with ... So how could I avoid this issue: Error: [illegal_argument_exception] mapper [hits] cannot be changed from type [long] to [integer] ? Thank you |
|
Created a new issue #197 hoping this will spur some comment since it looks like nobody is watching this closed issue any more. |
|
Hi, I found a temporal solution: curl -XPUT 'http://elasticsearch:9200/.kibana?pretty' -H 'Content-Type: application/json' -d' |
|
After my upgrades I also encountered blank page issues. To resolve my blank pages from integer and version: and This resolved my blank pages in management and visualization (from another post): curl -XPOST '${ELASTICSEARCH_HOST}/.kibana3/_update_by_query?pretty&wait_for_completion&refresh' -H 'Content-Type: application/json' -d' Finally, be sure to update your .kibana index in your kibana/config/kibana.yml to .kibana3. You can always rollback to .kibana if you like. |
and others
Hello!
Just tried installing. That's fine. But when going to the Timelion page it is blank.
I see this in the browser console:
Inspecting the response to the
http://IPADDRESS/elasticsearch/.kibana/_mapping/timelion-sheetcall I can see:I can see one related thing on the Kibana Issues to this but it's the other way around, int to long.
The text was updated successfully, but these errors were encountered: