# Empty "Shard Failures" error when first loading Kibana 4.4.1

**URL:** https://discuss.elastic.co/t/empty-shard-failures-error-when-first-loading-kibana-4-4-1/43518
**Category:** Kibana
**Created:** [March 4, 2016, 2:16pm UTC](https://discuss.elastic.co/t/empty-shard-failures-error-when-first-loading-kibana-4-4-1/43518 "2016-03-04T14:16:14Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![fern4lvarez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fern4lvarez/32/8284_2.png) [@fern4lvarez](https://discuss.elastic.co/u/fern4lvarez)
#### Post date: [March 4, 2016, 2:16pm UTC](https://discuss.elastic.co/t/empty-shard-failures-error-when-first-loading-kibana-4-4-1/43518/1 "2016-03-04T14:16:14Z")

</div>

Everytime I request Kibana 4.4.1 (using Elasticsearch 2.2.0) for first time, as in a new tab, I get the following screen:

 ![](https://us1.discourse-cdn.com/elastic/original/2X/e/e96291868aef670b8da92bf5addf80f2e73f2691.png)

Elasticsearch and Kibana logs don't show any error. Browser console (tested in Firefox) and Chrome, show following error:

```auto
config init commons.bundle.js:59454
complete in 198.27ms commons.bundle.js:59450:12
loading default index pattern commons.bundle.js:59454
Index Patterns: index pattern set to logstash-* commons.bundle.js:8976:17
complete in 400.22ms commons.bundle.js:59450:12
Error: indexPattern.fields is undefined
isSortable@https://elk.....net/bundles/kibana.bundle.js?v=9693:21355:8
getSort@https://elk.....net/bundles/kibana.bundle.js?v=9693:21362:47
__WEBPACK_AMD_DEFINE_RESULT__ </getSort.array@https://elk...net/bundles/kibana.bundle.js?v=9693:21377:15
getStateDefaults@https://elk....net/bundles/kibana.bundle.js?v=9693:20929:16
__WEBPACK_AMD_DEFINE_RESULT__ </<@https://elk...net/bundles/kibana.bundle.js?v=9693:20923:47
invoke@https://elk.....net/bundles/commons.bundle.js?v=9693:32090:15
$ControllerProvider/this.$get</</instantiate<@https://elk...net/bundles/commons.bundle.js?v=9693:36748:25
nodeLinkFn@https://elk...net/bundles/commons.bundle.js?v=9693:35860:37
compositeLinkFn@https://elk...net/bundles/commons.bundle.js?v=9693:35292:14
publicLinkFn@https://elk...net/bundles/commons.bundle.js?v=9693:35167:31
ngViewFillContentFactory/<.link@https://elk...net/bundles/commons.bundle.js?v=9693:58792:8
invokeLinkFn@https://elk...net/bundles/commons.bundle.js?v=9693:36401:10
nodeLinkFn@https://elk...net/bundles/commons.bundle.js?v=9693:35901:1
compositeLinkFn@https://elk...net/bundles/commons.bundle.js?v=9693:35292:14
publicLinkFn@https://elk...net/bundles/commons.bundle.js?v=9693:35167:31
createBoundTranscludeFn/boundTranscludeFn@https://elk...net/bundles/commons.bundle.js?v=9693:35311:1
controllersBoundTransclude@https://elk...net/bundles/commons.bundle.js?v=9693:35928:19
update@https://elk...net/bundles/commons.bundle.js?v=9693:58742:26
$RootScopeProvider/this.$get</Scope.prototype.$broadcast@https://elk...net/bundles/commons.bundle.js?v=9693:43923:16
commitRoute/<@https://elk...net/bundles/commons.bundle.js?v=9693:58426:16
processQueue@https://elk...net/bundles/commons.bundle.js?v=9693:42357:29
scheduleProcessQueue/<@https://elk...net/bundles/commons.bundle.js?v=9693:42373:28
$RootScopeProvider/this.$get</Scope.prototype.$eval@https://elk...net/bundles/commons.bundle.js?v=9693:43601:17
$RootScopeProvider/this.$get</Scope.prototype.$digest@https://elk...net/bundles/commons.bundle.js?v=9693:43412:16
$RootScopeProvider/this.$get</Scope.prototype.$apply@https://elk...net/bundles/commons.bundle.js?v=9693:43709:14
done@https://.../bundles/commons.bundle.js?v=9693:38158:37
completeRequest@https://.../bundles/commons.bundle.js?v=9693:38356:8
requestLoaded@https://.../bundles/commons.bundle.js?v=9693:38297:1
 <div ng-controller="chrome.$$rootControllerConstruct as kibana" class="application ng-scope" ng-class="'tab-' + chrome.getActiveTabId('-none-') + ' ' + chrome.getApplicationClasses()" ng-view=""> commons.bundle.js:40089:19

Error: Request to Elasticsearch failed: "Request Entity Too Large"
KbnError@https://elk...net/bundles/commons.bundle.js?v=9693:57416:21
RequestFailure@https://elk...net/bundles/commons.bundle.js?v=9693:57449:1
__WEBPACK_AMD_DEFINE_RESULT__ </</</<@https://elk...net/bundles/kibana.bundle.js?v=9693:78291:16
processQueue@https://elk...net/bundles/commons.bundle.js?v=9693:42357:29
scheduleProcessQueue/<@https://elk...net/bundles/commons.bundle.js?v=9693:42373:28
$RootScopeProvider/this.$get</Scope.prototype.$eval@https://elk...net/bundles/commons.bundle.js?v=9693:43601:17
$RootScopeProvider/this.$get</Scope.prototype.$digest@https://elk...net/bundles/commons.bundle.js?v=9693:43412:16
$RootScopeProvider/this.$get</Scope.prototype.$apply@https://elk...net/bundles/commons.bundle.js?v=9693:43709:14
done@https://elk...net/bundles/commons.bundle.js?v=9693:38158:37
completeRequest@https://elk...net/bundles/commons.bundle.js?v=9693:38356:8
requestLoaded@https://elk...net/bundles/commons.bundle.js?v=9693:38297:1

```

Most importantly, this seems to be a sporadic error, as if I click in any other tab, e.g. Visualize, and then Discover again, it shows the correct logging and elasticsearch data.

Any clue why we always get this initial screen?

EDIT:

For the record, I found similar reports, with no solution provided:

- [http://stackoverflow.com/questions/32253052/issue-in-loading-kibana-4](http://stackoverflow.com/questions/32253052/issue-in-loading-kibana-4)
- [Kibana doesn't display anything until all elasticsearch replica shards are allocated](https://discuss.elastic.co/t/kibana-doesnt-display-anything-until-all-elasticsearch-replica-shards-are-allocated/26930)

---

<div class="post-metadata">

### Author: ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)
#### Post date: [March 8, 2016, 12:00am UTC](https://discuss.elastic.co/t/empty-shard-failures-error-when-first-loading-kibana-4-4-1/43518/2 "2016-03-08T00:00:43Z")

</div>

That's strange. I haven't heard about yet, and I don't see anything in Github about it, but it definitely sounds like a bug of some sort. Would you mind [opening an issue on the repo](https://github.com/elastic/kibana/issues)?

---

<div class="post-metadata">

### Author: ![fern4lvarez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fern4lvarez/32/8284_2.png) [@fern4lvarez](https://discuss.elastic.co/u/fern4lvarez)
#### Post date: [March 8, 2016, 10:44am UTC](https://discuss.elastic.co/t/empty-shard-failures-error-when-first-loading-kibana-4-4-1/43518/3 "2016-03-08T10:44:32Z")

</div>

Sure, just did it: [https://github.com/elastic/kibana/issues/6460](https://github.com/elastic/kibana/issues/6460)

Thanks!

---

<div class="post-metadata">

### 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/empty-shard-failures-error-when-first-loading-kibana-4-4-1/43518/4 "2017-07-06T13:59:52Z")

</div>