# The First Run of Kibana 4 makes Elasticsearch crash **URL:** \ **Category:** Kibana\ **Created:** [June 17, 2015, 1:41pm UTC](https://discuss.elastic.co/t/the-first-run-of-kibana-4-makes-elasticsearch-crash/23843 "2015-06-17T13:41:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Aldian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aldian/32/906_2.png) [@Aldian](https://discuss.elastic.co/u/Aldian)\ **Post date:** [June 17, 2015, 1:41pm UTC](https://discuss.elastic.co/t/the-first-run-of-kibana-4-makes-elasticsearch-crash/23843/1 "2015-06-17T13:41:35Z")
Hi! I tried several times to migrate to kibana 4 but every time I access the interface and configure the indice pattern, kibana will load forever until Elasticsearch crashes around 10 min later. Then Kibana 4 shows an error page. Since this is a migration, I have about 500 open indices, most of them weighting around 60Mio. I am suspecting Kibana 4 to query them all at once, leading to heap space problems. How do I configure Kibana 4 to be less agressive toward Elasticsearch on its first run? Thanks for your help ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 18, 2015, 2:49am UTC](https://discuss.elastic.co/t/the-first-run-of-kibana-4-makes-elasticsearch-crash/23843/2 "2015-06-18T02:49:05Z")
What do the ES and KB logs show? ---
**Author:** ![Aldian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aldian/32/906_2.png) [@Aldian](https://discuss.elastic.co/u/Aldian)\ **Post date:** [June 18, 2015, 2:28pm UTC](https://discuss.elastic.co/t/the-first-run-of-kibana-4-makes-elasticsearch-crash/23843/3 "2015-06-18T14:28:21Z")
See here for the logs: [http://pastebin.com/UjTzdk4L](http://pastebin.com/UjTzdk4L) To be more specific, Elasticsearch does not completely crash, but it is as is: you have to use a kill with the "-9" flag to stop it, and before that, all queries will just handle forever until the following screen displays ![](https://us1.discourse-cdn.com/elastic/original/2X/b/ba630af53595fdc8ac192fbb7a1e58923017e163.PNG) I tried to give more memory to the vm, but did nothing. ---
**Author:** ![Bruce\_Lysik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bruce_lysik/32/2037_2.png) [@Bruce\_Lysik](https://discuss.elastic.co/u/Bruce_Lysik)\ **Post date:** [June 19, 2015, 5:57pm UTC](https://discuss.elastic.co/t/the-first-run-of-kibana-4-makes-elasticsearch-crash/23843/4 "2015-06-19T17:57:21Z")
It's probably because by default it's attempting to query logstash-\*, rather than time based indexing. You have to enable that. (Should be setup that way be default.) ---
**Author:** ![Aldian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aldian/32/906_2.png) [@Aldian](https://discuss.elastic.co/u/Aldian)\ **Post date:** [July 21, 2015, 1:12pm UTC](https://discuss.elastic.co/t/the-first-run-of-kibana-4-makes-elasticsearch-crash/23843/5 "2015-07-21T13:12:52Z")
The bug happens during the initial setup after I have specified this is a time based indexing. I never manged to reach the end of the initial setup with kibana 4 ---
**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, 2:16pm UTC](https://discuss.elastic.co/t/the-first-run-of-kibana-4-makes-elasticsearch-crash/23843/6 "2017-07-06T14:16:09Z")
Closed on July 6, 2017, 2:16pm UTC