# ES Request Timeout after 30000ms **URL:** \ **Category:** Kibana\ **Created:** [January 1, 2016, 7:57pm UTC](https://discuss.elastic.co/t/es-request-timeout-after-30000ms/38250 "2016-01-01T19:57:39Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\ **Post date:** [January 1, 2016, 7:57pm UTC](https://discuss.elastic.co/t/es-request-timeout-after-30000ms/38250/1 "2016-01-01T19:57:39Z")
I've seem to have lost connection from kibana 4.3 to ES 2.1 while idling over xmas, wondering how to resolve this as ES says: ``` [root@d1r1n1 ~]# curl -XGET "http://`hostname`:9200/_cluster/health?pretty" { "cluster_name" : "mxes_data", "status" : "green", "timed_out" : false, "number_of_nodes" : 14, "number_of_data_nodes" : 14, "active_primary_shards" : 141, "active_shards" : 282, "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 } ``` Kibana stdout shows this when restarted: ``` {"type":"log","@timestamp":"2016-01-01T19:19:59+00:00","tags":["listening","info"],"pid":19650,"message":"Server running at https://10.45.70.62:8080"} {"type":"log","@timestamp":"2016-01-01T19:20:29+00:00","tags":["status","plugin:elasticsearch","error"],"pid":19650,"name":"plugin:elasticsearch","state":"red","message":"Status changed from yellow to red - Request Timeout after 30000ms","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} ``` but I can see that kibana establishes a connection to ES which is renewed at intervals: > [root@d1r1n1 ~]# netstat -atp | grep kibana > tcp 0 25053 d1r1n1.nat.tdcfoo:elastic kibana.mxi.tdcfoo:35442 ESTABLISHED 7608/java > tcp 0 42950 d1r1n1.nat.tdcfoo:elastic kibana.mxi.tdcfoo:35426 LAST\_ACK - > [root@d1r1n1 ~]# netstat -atp | grep kibana > tcp 0 42949 d1r1n1.nat.tdcfoo:elastic kibana.mxi.tdcfoo:35446 ESTABLISHED 7608/java > tcp 0 42950 d1r1n1.nat.tdcfoo:elastic kibana.mxi.tdcfoo:35426 LAST\_ACK - > [root@d1r1n1 ~]# ping d1r1n1.nat.tdcfoo > PING d1r1n1.nat.tdcfoo (10.45.70.101) 56(84) bytes of data. > 64 bytes from d1r1n1.nat.tdcfoo (10.45.70.101): icmp\_seq=1 ttl=64 time=0.010 ms > 64 bytes from d1r1n1.nat.tdcfoo (10.45.70.101): icmp\_seq=2 ttl=64 time=0.010 ms > 64 bytes from d1r1n1.nat.tdcfoo (10.45.70.101): icmp\_seq=3 ttl=64 time=0.012 ms > 64 bytes from d1r1n1.nat.tdcfoo (10.45.70.101): icmp\_seq=4 ttl=64 time=0.012 ms > 64 bytes from d1r1n1.nat.tdcfoo (10.45.70.101): icmp\_seq=5 ttl=64 time=0.010 ms > 64 bytes from d1r1n1.nat.tdcfoo (10.45.70.101): icmp\_seq=6 ttl=64 time=0.011 ms > 64 bytes from d1r1n1.nat.tdcfoo (10.45.70.101): icmp\_seq=7 ttl=64 time=0.010 ms > 64 bytes from d1r1n1.nat.tdcfoo (10.45.70.101): icmp\_seq=8 ttl=64 time=0.009 ms > 64 bytes from d1r1n1.nat.tdcfoo (10.45.70.101): icmp\_seq=9 ttl=64 time=0.009 ms > ^C > --- d1r1n1.nat.tdcfoo ping statistics --- > 9 packets transmitted, 9 received, 0% packet loss, time 8961ms > rtt min/avg/max/mdev = 0.009/0.010/0.012/0.002 ms ---
**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:** [January 1, 2016, 11:50pm UTC](https://discuss.elastic.co/t/es-request-timeout-after-30000ms/38250/2 "2016-01-01T23:50:40Z")
Is there anything in your ES logs at the same time? ---
**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\ **Post date:** [January 2, 2016, 8:46am UTC](https://discuss.elastic.co/t/es-request-timeout-after-30000ms/38250/3 "2016-01-02T08:46:24Z")
No, nothing indicate that ES isn't working, I can see status,state and browse data + indices through ES:plugin:head/kopf and I see that new data/docs are been inserted from beats+logstash instances ---
**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\ **Post date:** [January 3, 2016, 10:11am UTC](https://discuss.elastic.co/t/es-request-timeout-after-30000ms/38250/4 "2016-01-03T10:11:36Z")
Finally figured it out. It turned out one of our hypervisor nodes, where my kibana VM was running somehow reverted an openvswitch to default mtu of 1500 instead of 9000, which kibana VM used, hence tcp replies never came back from ES nodes which also are using mtu of 9000 🙂 ---
**Author:** ![jalagrange](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jalagrange/32/8455_2.png) [@jalagrange](https://discuss.elastic.co/u/jalagrange)\ **Post date:** [March 14, 2016, 9:14am UTC](https://discuss.elastic.co/t/es-request-timeout-after-30000ms/38250/5 "2016-03-14T09:14:20Z")
Im having a very similar issue @stefws . Im getting: [error][status][plugin:elasticsearch] Status changed from green to red - Request Timeout after 1500ms How did you solve this? ---
**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:** [March 14, 2016, 9:37am UTC](https://discuss.elastic.co/t/es-request-timeout-after-30000ms/38250/6 "2016-03-14T09:37:16Z")
Per his last post, it was an MTU issue. ---
**Author:** ![jalagrange](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jalagrange/32/8455_2.png) [@jalagrange](https://discuss.elastic.co/u/jalagrange)\ **Post date:** [March 14, 2016, 9:42am UTC](https://discuss.elastic.co/t/es-request-timeout-after-30000ms/38250/7 "2016-03-14T09:42:07Z")
Thanks @warkolm . I found the commit in which this is fixed: [https://github.com/spalger/kibana/commit/dda1217a7fcb5c9bdf05cf7b3f9c29bf95424181](https://github.com/spalger/kibana/commit/dda1217a7fcb5c9bdf05cf7b3f9c29bf95424181) Essentially there is a request\_timeout setting in config/kibana.yml However this still doesn't solve the problem for me 😥 How do I edit MTU? This is my log.. it connects and disconnects intermitedly: 15:16:53.266] [error][status][plugin:elasticsearch] Status changed from green to red - Request Timeout after 30000ms log [15:16:57.278] [error][status][plugin:elasticsearch] Status changed from red to red - Request Timeout after 1500ms log [15:17:01.652] [info][status][plugin:elasticsearch] Status changed from red to green - Kibana index ready log [15:17:06.224] [error][status][plugin:elasticsearch] Status changed from green to red - Request Timeout after 1500ms log [15:17:39.414] [error][status][plugin:elasticsearch] Status changed from red to red - Request Timeout after 30000ms log [15:17:43.818] [info][status][plugin:elasticsearch] Status changed from red to green - Kibana index ready log [15:17:48.393] [error][status][plugin:elasticsearch] Status changed from green to red - Request Timeout after 1500ms log [15:18:21.504] [error][status][plugin:elasticsearch] Status changed from red to red - Request Timeout after 30000ms ---
**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/es-request-timeout-after-30000ms/38250/9 "2017-07-06T13:59:14Z")