# Request to Elasticsearch failed **URL:** \ **Category:** Kibana\ **Created:** [November 1, 2018, 1:22am UTC](https://discuss.elastic.co/t/request-to-elasticsearch-failed/154947 "2018-11-01T01:22:45Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![SteveNeedsHelp](https://avatars.discourse-cdn.com/v4/letter/s/bc79bd/32.png) [@SteveNeedsHelp](https://discuss.elastic.co/u/SteveNeedsHelp)\ **Post date:** [November 1, 2018, 1:22am UTC](https://discuss.elastic.co/t/request-to-elasticsearch-failed/154947/1 "2018-11-01T01:22:46Z")
Kibana 6.4.2 ElasticSearch 6.4.2 We are getting this error in Kibana having left a dashboard connected overnight Version: 6.4.2 Build: 18010 Error: Request to Elasticsearch failed: {"error":{"root\_cause":,"type":"search\_phase\_execution\_exception","reason":"all shards failed","phase":"query","grouped":true,"failed\_shards":},"status":503} at [http://au-melaqssi02p:5601/bundles/commons.bundle.js:3:1095506](http://au-melaqssi02p:5601/bundles/commons.bundle.js:3:1095506) at Function.Promise.try ([http://au-melaqssi02p:5601/bundles/commons.bundle.js:3:807416](http://au-melaqssi02p:5601/bundles/commons.bundle.js:3:807416)) at [http://au-melaqssi02p:5601/bundles/commons.bundle.js:3:806787](http://au-melaqssi02p:5601/bundles/commons.bundle.js:3:806787) at Array.map () at Function.Promise.map ([http://au-melaqssi02p:5601/bundles/commons.bundle.js:3:806745](http://au-melaqssi02p:5601/bundles/commons.bundle.js:3:806745)) at callResponseHandlers ([http://au-melaqssi02p:5601/bundles/commons.bundle.js:3:1094865](http://au-melaqssi02p:5601/bundles/commons.bundle.js:3:1094865)) at [http://au-melaqssi02p:5601/bundles/commons.bundle.js:3:1080844](http://au-melaqssi02p:5601/bundles/commons.bundle.js:3:1080844) at processQueue ([http://au-melaqssi02p:5601/bundles/vendors.bundle.js:211:199684](http://au-melaqssi02p:5601/bundles/vendors.bundle.js:211:199684)) at [http://au-melaqssi02p:5601/bundles/vendors.bundle.js:211:200647](http://au-melaqssi02p:5601/bundles/vendors.bundle.js:211:200647) at Scope.$digest ([http://au-melaqssi02p:5601/bundles/vendors.bundle.js:211:210409](http://au-melaqssi02p:5601/bundles/vendors.bundle.js:211:210409)) at [http://au-melaqssi02p:5601/bundles/vendors.bundle.js:211:212941](http://au-melaqssi02p:5601/bundles/vendors.bundle.js:211:212941) at completeOutstandingRequest ([http://au-melaqssi02p:5601/bundles/vendors.bundle.js:211:64424](http://au-melaqssi02p:5601/bundles/vendors.bundle.js:211:64424)) at [http://au-melaqssi02p:5601/bundles/vendors.bundle.js:211:67265](http://au-melaqssi02p:5601/bundles/vendors.bundle.js:211:67265) The Elastic log doesn't have any errors, only the following warnings: - Line 297: [2018-10-31T12:51:26,111][WARN][o.e.g.GatewayAllocator$InternalPrimaryShardAllocator] [AU-MELAQSSI02P] [index\_jobs\_data\_2018\_10\_31t05\_00\_27][1]: failed to list shard for shard\_started on node [TnFjt3tCRRWY3mW1EngsCw] Line 470: [2018-10-31T13:03:27,187][WARN][o.e.g.GatewayAllocator$InternalPrimaryShardAllocator] [AU-MELAQSSI02P] [index\_dictionary\_errors\_2018\_10\_30t17\_12\_33][0]: failed to list shard for shard\_started on node [TnFjt3tCRRWY3mW1EngsCw] Line 547: [2018-10-31T13:04:44,745][WARN][o.e.c.a.s.ShardStateAction] [AU-MELAQSSI02P] unexpected failure while sending request [internal:cluster/shard/started] to [{AU-MELAQSSI02P}{TnFjt3tCRRWY3mW1EngsCw}{BGjzZX9hQxaUZ-tatVOIKA}{127.0.0.1}{127.0.0.1:9300}{ml.machine\_memory=17179398144, xpack.installed=true, ml.max\_open\_jobs=20, ml.enabled=true}] for shard entry [StartedShardEntry{shardId [[index\_integrity\_gct\_data\_2018\_10\_24t11\_44\_14][3]], allocationId [4ijX0SqwQjmKTzEDGhcykg], message [after existing recovery]}] Line 564: [2018-10-31T13:04:44,745][WARN][o.e.c.a.s.ShardStateAction] [AU-MELAQSSI02P] unexpected failure while sending request [internal:cluster/shard/started] to [{AU-MELAQSSI02P}{TnFjt3tCRRWY3mW1EngsCw}{BGjzZX9hQxaUZ-tatVOIKA}{127.0.0.1}{127.0.0.1:9300}{ml.machine\_memory=17179398144, xpack.installed=true, ml.max\_open\_jobs=20, ml.enabled=true}] for shard entry [StartedShardEntry{shardId [[index\_integrity\_gct\_data\_2018\_10\_24t11\_44\_14][0]], allocationId [yv4XJc6MSeuvdbJIiMM91A], message [after existing recovery]}] Line 625: [2018-10-31T13:05:16,389][WARN][o.e.g.GatewayAllocator$InternalPrimaryShardAllocator] [AU-MELAQSSI02P] [index\_jobs\_errors\_2018\_10\_30t22\_00\_32][2]: failed to list shard for shard\_started on node [TnFjt3tCRRWY3mW1EngsCw] Line 747: [2018-10-31T13:19:08,787][WARN][o.e.g.GatewayAllocator$InternalPrimaryShardAllocator] [AU-MELAQSSI02P] [index\_jobs\_errors\_2018\_10\_30t22\_00\_32][2]: failed to list shard for shard\_started on node [TnFjt3tCRRWY3mW1EngsCw] Line 977: [2018-10-31T13:34:50,630][WARN][o.e.g.GatewayAllocator$InternalPrimaryShardAllocator] [AU-MELAQSSI02P] [index\_integrity\_rf\_active\_delimiters\_errors\_2018\_10\_30t22\_00\_32][0]: failed to list shard for shard\_started on node [TnFjt3tCRRWY3mW1EngsCw] Line 1201: [2018-10-31T13:51:52,536][WARN][o.e.g.GatewayAllocator$InternalPrimaryShardAllocator] [AU-MELAQSSI02P] [index\_jobs\_errors\_2018\_10\_30t22\_00\_32][0]: failed to list shard for shard\_started on node [TnFjt3tCRRWY3mW1EngsCw] Line 1272: [2018-10-31T13:51:53,272][WARN][o.e.g.GatewayAllocator$InternalPrimaryShardAllocator] [AU-MELAQSSI02P] [index\_integrity\_rf\_active\_delimiters\_data\_2018\_10\_25t13\_02\_09][3]: failed to list shard for shard\_started on node [TnFjt3tCRRWY3mW1EngsCw] Line 1343: [2018-10-31T13:51:53,288][WARN][o.e.g.GatewayAllocator$InternalPrimaryShardAllocator] [AU-MELAQSSI02P] [index\_integrity\_rf\_active\_delimiters\_data\_2018\_10\_25t13\_02\_09][0]: failed to list shard for shard\_started on node [TnFjt3tCRRWY3mW1EngsCw] There is nothing of interest in the Kibana logs. Any ideas why this error occurred? Thanks ---
**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 2, 2018, 3:39am UTC](https://discuss.elastic.co/t/request-to-elasticsearch-failed/154947/2 "2018-11-02T03:39:58Z")
@Stacey_Gammon is this a known issue with leaving dashboards running overnight on 6.4.2 ? Also this might depend on various number of factors like - what OS are you running, how much memory is assigned to the machine , are there any other processes hogging the system etc. Cheers Rashmi ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 30, 2018, 3:54am UTC](https://discuss.elastic.co/t/request-to-elasticsearch-failed/154947/3 "2018-11-30T03:54:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.