# Kibana warning **URL:** \ **Category:** Kibana\ **Created:** [March 9, 2016, 7:43am UTC](https://discuss.elastic.co/t/kibana-warning/43872 "2016-03-09T07:43:07Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Kishore](https://avatars.discourse-cdn.com/v4/letter/k/8edcca/32.png) [@Kishore](https://discuss.elastic.co/u/Kishore)\ **Post date:** [March 9, 2016, 7:43am UTC](https://discuss.elastic.co/t/kibana-warning/43872/1 "2016-03-09T07:43:07Z")
Kibana is throwing below warning while loading _"Courier Fetch: 5 of 5 shards failed."_ Below is the elasticsearch log _[2016-03-09 02:39:37,947][DEBUG][action.search.type] [ELK-ES-CLUSTER-NODE1] [541751] Failed to execute fetch phase_ _RemoteTransportException[[ELK-ES-CLUSTER-NODE2][**.**. **.** :9300][indices:data/read/search[phase/fetch/id]]]; nested: ElasticsearchException[java.lang.IllegalStateException: Field data loading is forbidden on Date]; nested: NotSerializableExceptionWrapper[java.lang.IllegalStateException: Field data loading is forbidden on Date]; nested: IllegalStateException[Field data loading is forbidden on Date];_ _Caused by: ElasticsearchException[java.lang.IllegalStateException: Field data loading is forbidden on Date]; nested: NotSerializableExceptionWrapper[java.lang.IllegalStateException: Field data loading is forbidden on Date]; nested: IllegalStateException[Field data loading is forbidden on Date];_ Kindly help me in fixing this issue. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [March 9, 2016, 8:21am UTC](https://discuss.elastic.co/t/kibana-warning/43872/2 "2016-03-09T08:21:44Z")
Kibana uses the HTTP protocol, so must be configured to connect to port 9200, not 9300. ---
**Author:** ![Kishore](https://avatars.discourse-cdn.com/v4/letter/k/8edcca/32.png) [@Kishore](https://discuss.elastic.co/u/Kishore)\ **Post date:** [March 9, 2016, 8:28am UTC](https://discuss.elastic.co/t/kibana-warning/43872/3 "2016-03-09T08:28:38Z")
Thanks Christian for your quick response, Kindly guide me to configure this change. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [March 9, 2016, 8:32am UTC](https://discuss.elastic.co/t/kibana-warning/43872/4 "2016-03-09T08:32:17Z")
Sorry, I misread and thought the error was in the Kibana log. Which version of Elasticsearch and kibana are you using? How many nodes do you have in the cluster? What does your mapping for the index look like? ---
**Author:** ![Kishore](https://avatars.discourse-cdn.com/v4/letter/k/8edcca/32.png) [@Kishore](https://discuss.elastic.co/u/Kishore)\ **Post date:** [March 9, 2016, 9:07am UTC](https://discuss.elastic.co/t/kibana-warning/43872/5 "2016-03-09T09:07:17Z")
**Versions** Elasticsearch - 2.1.1 ( 2 node cluster) Kibana - 4.3.1 Part of Mapping info \_{"logstash-2016.03.09":{"mappings":{"sepm":{"_all":{"enabled":true,"omit\_norms":true},"dynamic\_templates":[{"message\_field":{"mapping":{"fielddata":{"format":"disabled"},"index":"analyzed","omit\_norms":true,"type":"string"},"match":"message","match\_mapping\_type":"string"}},{"string\_fields":{"mapping":{"fielddata":{"format":"disabled"},"index":"analyzed","omit\_norms":true,"type":"string","fields":{"raw":{"ignore\_above":256,"index":"not\_analyzed","type":"string","doc\_values":true}}},"match":"","match\_mapping\_type":"string"}},{"float\_fields":{"mapping":{"type":"float","doc\_values":true},"match":"","match\_mapping\_type":"float"}},{"double\_fields":{"mapping":{"type":"double","doc\_values":true},"match":"","match\_mapping\_type":"double"}},{"byte\_fields":{"mapping":{"type":"byte","doc\_values":true},"match":"","match\_mapping\_type":"byte"}},{"short\_fields":{"mapping":{"type":"short","doc\_values":true},"match":"","match\_mapping\_type":"short"}},{"integer\_fields":{"mapping":{"type":"integer","doc\_values":true},"match":"","match\_mapping\_type":"integer"}},{"long\_fields":{"mapping":{"type":"long","doc\_values":true},"match":"","match\_mapping\_type":"long"}},{"date\_fields":{"mapping":{"type":"date","doc\_values":true},"match":"","match\_mapping\_type":"date"}},{"geo\_point\_fields":{"mapping":{"type":"geo\_point","doc\_values":true},"match":"\*","match\_mapping\_type":"geo\_point"}}],"properties":{"@timestamp":{"type":"date","format":"strict\_date\_optional\_time||epoch\_millis"},"@version":{"type":"string","index":"not\_analyzed"},"Begin\_Date":{"type":"string","norms":{"enabled":false},"fielddata":{"format":"disabled"},"fields":{"raw":{"type":"string","index":"not\_analyzed","ignore\_above":256}}},_ ---
**Author:** ![Kishore](https://avatars.discourse-cdn.com/v4/letter/k/8edcca/32.png) [@Kishore](https://discuss.elastic.co/u/Kishore)\ **Post date:** [March 9, 2016, 9:51am UTC](https://discuss.elastic.co/t/kibana-warning/43872/6 "2016-03-09T09:51:24Z")
I have seen following conflict at Kibana dashboard "_Mapping conflict! A field is defined as several types (string, integer, etc) across the indices that match this pattern. You may still be able to use these conflict fields in parts of Kibana, but they will be unavailable for functions that require Kibana to know their type. Correcting this issue will require reindexing your data."_ and i have noticed below warning for one of the fields in Indices tab. ![](https://us1.discourse-cdn.com/elastic/original/2X/7/784e8e503b6da2a1400116f0042bc789e59b6418.png) ---
**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\ **Post date:** [March 9, 2016, 8:01pm UTC](https://discuss.elastic.co/t/kibana-warning/43872/7 "2016-03-09T20:01:15Z")
That conflict is a normal error to see if the field `received_at` is defined as different types in different indices. From the previous messages, it seems like your mappings may be in a bad state. Is elasticsearch starting up ok? Are you getting any actual errors in your elasticsearch logs? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:59pm UTC](https://discuss.elastic.co/t/kibana-warning/43872/8 "2017-07-06T13:59:39Z")