# Kibana 5.6.6 Crashing After 30s **URL:** \ **Category:** Kibana\ **Created:** [November 5, 2019, 9:17pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678 "2019-11-05T21:17:30Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![ChuckNorris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chucknorris/32/57209_2.png) [@ChuckNorris](https://discuss.elastic.co/u/ChuckNorris)\ **Post date:** [November 5, 2019, 9:17pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/1 "2019-11-05T21:17:31Z")
After launching Kibana 5.6.6 it appears to crash unexpectedly. I can perform a couple of searches before it times out. We attempted to increase the timeout rate in the config file but that did not appear to help any suggestions would be greatly appreciated: ``` log [14:51:27.420] [error][status][plugin:elasticsearch@5.6.6] Status changed from green to red - Request Timeout after 3000ms log [14:51:27.423] [error][status][ui settings] Status changed from green to red - Elasticsearch plugin is red log [14:52:17.170] [error][admin][elasticsearch] Request error, retryingGET http://x.x.x.x:9200/_nodes?filter_path=nodes.*.version%2Cnodes.*.http.publish_address%2Cnodes.*.ip => socket hang up log [14:52:47.170] [error][status][plugin:elasticsearch@5.6.6] Status changed from red to red - Request Timeout after 60000ms log [14:52:49.359] [error][admin][elasticsearch] Request error, retryingPOST http://x.x.x.x:9200/.kibana/_msearch => socket hang up log [14:53:19.363] [warning][admin][elasticsearch] Unable to revive connection: http://x.x.x.x:9200/ log [14:53:19.675] [error][admin][elasticsearch] Request error, retryingGET http://x.x.x.x:9200/_nodes?filter_path=nodes.*.version%2Cnodes.*.http.publish_address%2Cnodes.*.ip => socket hang up log [14:53:49.678] [warning][admin][elasticsearch] Unable to revive connection: http://x.x.x.x:9200/ log [14:54:22.178] [warning][admin][elasticsearch] Unable to revive connection: http://x.x.x.x:9200/ log [14:54:22.179] [warning][admin][elasticsearch] No living connections log [14:54:22.181] [error][status][plugin:elasticsearch@5.6.6] Status changed from red to red - No Living connections log [14:54:54.685] [warning][admin][elasticsearch] Unable to revive connection: http://x.x.x.x:9200/ log [14:54:54.686] [warning][admin][elasticsearch] No living connections log [14:55:27.190] [warning][admin][elasticsearch] Unable to revive connection: http://x.x.x.x:9200/ log [14:55:27.192] [warning][admin][elasticsearch] No living connections log [14:55:59.698] [warning][admin][elasticsearch] Unable to revive connection: http://x.x.x.x:9200/ log [14:55:59.699] [warning][admin][elasticsearch] No living connections log [14:56:32.202] [warning][admin][elasticsearch] Unable to revive connection: http://x.x.x.x:9200/ ``` Also seeing this in Kibana UI: ``` Error: Request Timeout after 60000ms at http://x.x.x.x:5601/bundles/kibana.bundle.js?v=15605:13:4431 at http://x.x.x.x:5601/bundles/kibana.bundle.js?v=15605:13:4852 ``` ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [November 12, 2019, 4:52am UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/2 "2019-11-12T04:52:19Z")
@tylersmalley or @jbudz - can shed some light here. I tried spinning a cloud 5.6 cluster and it works without a crash as mentioned here. Thanks Rashmi ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [November 12, 2019, 5:08am UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/3 "2019-11-12T05:08:07Z")
It's not Kibana that is crashing, it's that Kibana is unable to reach Elasticsearch. Can you check the Cluster Health Elasticsearch API from the server Kibana is on? (replacing `x.x.x.x` with your IP) `curl -X GET "http://x.x.x.x:9200/_cluster/health&pretty"` ---
**Author:** ![ChuckNorris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chucknorris/32/57209_2.png) [@ChuckNorris](https://discuss.elastic.co/u/ChuckNorris)\ **Post date:** [November 15, 2019, 7:41pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/4 "2019-11-15T19:41:38Z")
Tyler, The cluster health is green but as soon as I launch Kibana it wont stay up long once we start running searches. I have another UI to search elastic that is SQL based and I never have any issues but as soon as I start using Kibana and begin searching is when the issues begin. { "cluster\_name": "MY-CLUSTER01", "status": "green", "timed\_out": false, "number\_of\_nodes": 9, "number\_of\_data\_nodes": 9, "active\_primary\_shards": 300, "active\_shards": 600, "relocating\_shards": 0, "initializing\_shards": 0, "unassigned\_shards": 0, "delayed\_unassigned\_shards": 0, "number\_of\_pending\_tasks": 0, "number\_of\_in\_flight\_fetch": 0, "task\_max\_waiting\_in\_queue\_millis": 0, "active\_shards\_percent\_as\_number": 100.0 } ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [November 15, 2019, 7:52pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/5 "2019-11-15T19:52:44Z")
What plugins do you have installed? ---
**Author:** ![ChuckNorris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chucknorris/32/57209_2.png) [@ChuckNorris](https://discuss.elastic.co/u/ChuckNorris)\ **Post date:** [November 15, 2019, 8:03pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/6 "2019-11-15T20:03:57Z")
None that I'm aware of. ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [November 15, 2019, 8:18pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/7 "2019-11-15T20:18:05Z")
Is Kibana hitting Elasticsearch directly, or do you have a load balancer or anything between? I would check that and the Elasticsearch logs. Kibana is getting a socket timeout on that connection so no much I can think to do on the Kibana side. ---
**Author:** ![ChuckNorris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chucknorris/32/57209_2.png) [@ChuckNorris](https://discuss.elastic.co/u/ChuckNorris)\ **Post date:** [November 15, 2019, 8:59pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/8 "2019-11-15T20:59:24Z")
Kibana is hitting Elastic directly both are on separate boxes but they are on the same subnet. No load balancer between them. ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [November 15, 2019, 9:58pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/9 "2019-11-15T21:58:36Z")
Is this taking down the Elasticsearch cluster? Once this happens, what does the `_cluster/health` look like then? ---
**Author:** ![ChuckNorris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chucknorris/32/57209_2.png) [@ChuckNorris](https://discuss.elastic.co/u/ChuckNorris)\ **Post date:** [November 20, 2019, 5:22pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/10 "2019-11-20T17:22:39Z")
When we start running intensive searches I am unable to use postman or curl on the server to get cluster health its almost like the indexer is so busy it cant even run the cluster health command: localhost:9200/\_cluster/health. I was alerted through a third party app that the cluster state is critical so I would assume it is in a Red state right now. Any suggestions on what could be causing this? ---
**Author:** ![ChuckNorris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chucknorris/32/57209_2.png) [@ChuckNorris](https://discuss.elastic.co/u/ChuckNorris)\ **Post date:** [November 20, 2019, 7:59pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/11 "2019-11-20T19:59:29Z")
Update: I did confirm that the cluster did go red we are still in a yellow state but expect to go back to green soon. ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [November 21, 2019, 6:13pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/12 "2019-11-21T18:13:21Z")
Thanks for the update . Keep us posted. ---
**Author:** ![ChuckNorris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chucknorris/32/57209_2.png) [@ChuckNorris](https://discuss.elastic.co/u/ChuckNorris)\ **Post date:** [November 21, 2019, 7:56pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/13 "2019-11-21T19:56:04Z")
The problem is Kibana wont stay up without the cluster going red. However we would like to use Kibana without it crashing. What could we do to make sure it remains stable when performing searches on it? What I'm think is happening is that when we run a large search its opening closed indecies and causes the JVM to crash... ---
**Author:** ![ChuckNorris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chucknorris/32/57209_2.png) [@ChuckNorris](https://discuss.elastic.co/u/ChuckNorris)\ **Post date:** [November 25, 2019, 2:25pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/14 "2019-11-25T14:25:43Z")
@rashmi or @tylersmalley any suggestions? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 23, 2019, 2:26pm UTC](https://discuss.elastic.co/t/kibana-5-6-6-crashing-after-30s/206678/15 "2019-12-23T14:26:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.