# Some indices broken after updating Kibana and Elasticsearch
**URL:** https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149
**Category:** Kibana
**Created:** [June 13, 2017, 7:27am UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149 "2017-06-13T07:27:01Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@Dmytro\_Orel](https://discuss.elastic.co/u/Dmytro_Orel)
#### Post date: [June 13, 2017, 7:27am UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/1 "2017-06-13T07:27:01Z")
Hi there,
I recently updated Kibana from 4.5 to 5.4.1 and Elasticsearch from 2.3 to 5.4.1. After this some indices start look broken:
1. in 'Discover' I get '"field" is a required parameter' message and it stays in 'Searching' state even if I use time range so small there are no entries in it;
2. existing visualizations and dashboards don't show any data and I get the same message as in previous item; when I try to add new visualization, it does not recognize any string/number/timestamp field, only geo\_point;
3. if I open corresponding index pattern, no fields are searchable or aggregatable (except geo\_point); refreshing field list does not help;
4. if I create new index through API, the result is the same as in item 3 (does not matter what fields it contains); I use nuget libraries [Elasticsearch.Net](http://Elasticsearch.Net) and NEST, v5.4.0 both; and yes, I use Keyword/Text attributes.
There are the indices that work correct however. The only difference that I see between them is that those that stopped working contain geo\_point field (but this field is the last thing working for them).
If it's the wrong category, please move it to the correct one.
Thanks in advance!
---
### Author:  [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)
#### Post date: [June 13, 2017, 12:28pm UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/2 "2017-06-13T12:28:48Z")
Hey @Dmytro_Orel have you tried refreshing your index patterns? To do so, if you click "Management" -\> "Index Patterns"
and then select your index pattern to the left and click "Refresh fields list"
---
### Author:  [@Dmytro\_Orel](https://discuss.elastic.co/u/Dmytro_Orel)
#### Post date: [June 13, 2017, 12:50pm UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/3 "2017-06-13T12:50:04Z")
hi,
as I said in item 3, refresh fields didn't help.
---
### Author:  [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)
#### Post date: [June 13, 2017, 12:51pm UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/4 "2017-06-13T12:51:41Z")
@Dmytro_Orel would you mind describing the upgrade process that you followed?
---
### Author:  [@Dmytro\_Orel](https://discuss.elastic.co/u/Dmytro_Orel)
#### Post date: [June 13, 2017, 1:43pm UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/5 "2017-06-13T13:43:13Z")
sorry for the delay.
a standard procedure, described in docs: update debian repo definition, stop, apt-get install, start, first for Elasticsearch, than for Kibana. since we have only 1 VM, not a cluster, i thought it's not needed to disable shard allocation.
before updating Elasticsearch i installed migration helper plugin and checked that everything is green, except notification that from/to won't be available for geo\_point any more (we don't use from/to anyway).
---
### Author:  [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)
#### Post date: [June 13, 2017, 4:30pm UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/6 "2017-06-13T16:30:04Z")
@Dmytro_Orel I'm sorry to tell you that this is being caused by [https://github.com/elastic/elasticsearch/issues/24275](https://github.com/elastic/elasticsearch/issues/24275) which is unresolved at this time. The only work-around that we have at this moment is to reindex your data, or wait for Kibana 5.5 to be released which won't rely on the \_field\_stats to determine index patterns.
---
### Author:  [@Dmytro\_Orel](https://discuss.elastic.co/u/Dmytro_Orel)
#### Post date: [June 14, 2017, 6:56am UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/7 "2017-06-14T06:56:14Z")
just a basic reindex like first example in [guide](https://www.elastic.co/guide/en/elasticsearch/reference/5.4/docs-reindex.html), or something more sophisticated?
and by the way, how will it fix issue with _creating new index_? just to remind:
4. if I create new index through API, the result is the same as in item 3 (does not matter what fields it contains); I use nuget libraries [Elasticsearch.Net](http://Elasticsearch.Net) and NEST, v5.4.0 both; and yes, I use Keyword/Text attributes.
---
### Author:  [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)
#### Post date: [June 14, 2017, 12:57pm UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/8 "2017-06-14T12:57:56Z")
@Dmytro_Orel the basic reindex like the first example in the guide will work.
Regarding item 4, if you create a new index using the API and then created an index pattern in Kibana using the exact index name without wildcard names, what are you seeing?
---
### Author:  [@Dmytro\_Orel](https://discuss.elastic.co/u/Dmytro_Orel)
#### Post date: [June 14, 2017, 1:09pm UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/9 "2017-06-14T13:09:05Z")
here's the result:
UPD: fixed after i posted some dummy data there.
proceeding with reindex then.
---
### Author:  [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)
#### Post date: [June 14, 2017, 1:15pm UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/10 "2017-06-14T13:15:15Z")
@Dmytro_Orel Interesting... would you mind creating a basic index using CURL to determine if this is being caused by the client libraries or Elasticsearch itself? Does this happen when creating indices without the geo fields?
---
### Author:  [@Dmytro\_Orel](https://discuss.elastic.co/u/Dmytro_Orel)
#### Post date: [June 14, 2017, 1:34pm UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/11 "2017-06-14T13:34:34Z")
the screenshot is for index w/o geo fields (all of the fields are on screenshot actually).
same happens with CURL:
curl -XPUT 'localhost:9200/test2?pretty' -H 'Content-Type: application/json' -d'
{
"settings" : {
"number\_of\_shards" : 1
},
"mappings" : {
"type1" : {
"properties" : {
"field1" : { "type" : "text" },
"field2" : { "type" : "date" }
}
}
}
}
'
---
### Author:  [@Dmytro\_Orel](https://discuss.elastic.co/u/Dmytro_Orel)
#### Post date: [June 14, 2017, 1:44pm UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/12 "2017-06-14T13:44:06Z")
reindex to new did the trick, thank you so much!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 12, 2017, 1:44pm UTC](https://discuss.elastic.co/t/some-indices-broken-after-updating-kibana-and-elasticsearch/89149/13 "2017-07-12T13:44:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.