# Unable To connect kibana 6.4 with elasticsearch 6.4

**URL:** <https://discuss.elastic.co/t/unable-to-connect-kibana-6-4-with-elasticsearch-6-4/149399>\
**Category:** Kibana\
**Created:** [September 21, 2018, 6:38am UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-6-4-with-elasticsearch-6-4/149399 "2018-09-21T06:38:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrumeshkumar](https://avatars.discourse-cdn.com/v4/letter/m/f9ae1b/32.png) [@mrumeshkumar](https://discuss.elastic.co/u/mrumeshkumar)\
**Post date:** [September 21, 2018, 6:38am UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-6-4-with-elasticsearch-6-4/149399/1 "2018-09-21T06:38:12Z")

</div>

Hi All,

I have 3 instance of elastic search 6.4.0 . on three different servers.

Node Configuration:

ALPR1DESEARCH01  
node.data: false  
node.ingest: false  
node.master: true  
ALPR1DESEARCH02  
node.data: true  
node.ingest: false  
node.master: false  
ALPR1DESEARCH03  
node.data: false  
node.ingest: true  
node.master: false

Questions: can any one help me on below mentioned problems to solve.

1. Which node on elastic search i need to connect kibana ?

2. I have installed kibana 6.4 and connect that to master node "ALPR1DESEARCH01" but i am geeting below mentioned error and not able to use kibana dev toll, its always showing meesage "Help us improve the Elastic Stack by providing basic feature usage statistics? We will never share this data outside of Elastic." and when click on yes or no nothing is working.

* * *

Microsoft Windows [Version 10.0.14393]  
(c) 2016 Microsoft Corporation. All rights reserved.

C:\kibana-6.4.0\bin\>kibana.bat  
log [06:20:59.793] [info][status][plugin:reporting@6.4.0] Status changed from yellow to green - Ready  
log [06:20:59.809] [info][kibana-monitoring][monitoring-ui] Starting monitoring stats collection  
log [06:20:59.809] [info][status][plugin:security@6.4.0] Status changed from yellow to green - Ready

log [06:20:59.825] [warning][stats-collection] Unable to fetch data from kibana collector  
error [06:20:59.840] [warning][stats-collection] [no\_shard\_available\_action\_exception] No shard available for [get [.kibana][doc][config:6.4.0]: routing [null]] :: {"path":"/.kibana/doc/config%3A6.4.0","query":{},"statusCode":503,"response":"{"error":{"root\_cause":[{"type":"no\_shard\_available\_action\_exception","reason":"No shard available for [get [.kibana][doc][config:6.4.0]: routing [null]]"}],"type":"no\_shard\_available\_action\_exception","reason":"No shard available for [get [.kibana][doc][config:6.4.0]: routing [null]]"},"status":503}"}  
at respond (C:\kibana-6.4.0\node\_modules\elasticsearch\src\lib\transport.js:307:15)  
at checkRespForFailure (C:\kibana-6.4.0\node\_modules\elasticsearch\src\lib\transport.js:266:7)  
at HttpConnector. (C:\kibana-6.4.0\node\_modules\elasticsearch\src\lib\connectors\http.js:159:7)  
at IncomingMessage.bound (C:\kibana-6.4.0\node\_modules\elasticsearch\node\_modules\lodash\dist\lodash.js:729:21)  
at emitNone (events.js:111:20)  
at IncomingMessage.emit (events.js:208:7)  
at endReadableNT (\_stream\_readable.js:1064:12)  
at \_combinedTickCallback (internal/process/next\_tick.js:138:11)  
at process.\_tickCallback (internal/process/next\_tick.js:180:9)  
log [06:20:59.840] [warning][stats-collection] Unable to fetch data from kibana\_settings collector  
log [06:20:59.871] [info][license][xpack] Imported license information from Elasticsearch for the [monitoring] cluster: mode: basic | status: active  
error [06:21:09.820] [warning][stats-collection] [search\_phase\_execution\_exception] all shards failed :: {"path":"/.kibana/\_search","query":{"ignore\_unavailable":true,"filter\_path":"aggregations.types.buckets"},"body":"{"size":0,"query":{"terms":{"type":["dashboard","visualization","search","index-pattern","graph-workspace","timelion-sheet"]}},"aggs":{"types":{"terms":{"field":"type","size":6}}}}","statusCode":503,"response":"{"error":{"root\_cause":[],"type":"search\_phase\_execution\_exception","reason":"all shards failed","phase":"query","grouped":true,"failed\_shards":[]},"status":503}"}  
at respond (C:\kibana-6.4.0\node\_modules\elasticsearch\src\lib\transport.js:307:15)  
at checkRespForFailure (C:\kibana-6.4.0\node\_modules\elasticsearch\src\lib\transport.js:266:7)  
at HttpConnector. (C:\kibana-6.4.0\node\_modules\elasticsearch\src\lib\connectors\http.js:159:7)  
at IncomingMessage.bound (C:\kibana-6.4.0\node\_modules\elasticsearch\node\_modules\lodash\dist\lodash.js:729:21)  
at emitNone (events.js:111:20)  
at IncomingMessage.emit (events.js:208:7)  
at endReadableNT (\_stream\_readable.js:1064:12)  
at \_combinedTickCallback (internal/process/next\_tick.js:138:11)  
at process.\_tickCallback (internal/process/next\_tick.js:180:9)  
log [06:21:09.820] [warning][stats-collection] Unable to fetch data from kibana collector  
error [06:21:09.820] [warning][stats-collection] [no\_shard\_available\_action\_exception] No shard available for [get [.kibana][doc][config:6.4.0]: routing [null]] :: {"path":"/.kibana/doc/config%3A6.4.0","query":{},"statusCode":503,"response":"{"error":{"root\_cause":[{"type":"no\_shard\_available\_action\_exception","reason":"No shard available for [get [.kibana][doc][config:6.4.0]: routing [null]]"}],"type":"no\_shard\_available\_action\_exception","reason":"No shard available for [get [.kibana][doc][config:6.4.0]: routing [null]]"},"status":503}"}  
at respond (C:\kibana-6.4.0\node\_modules\elasticsearch\src\lib\transport.js:307:15)  
at checkRespForFailure (C:\kibana-6.4.0\node\_modules\elasticsearch\src\lib\transport.js:266:7)  
at HttpConnector. (C:\kibana-6.4.0\node\_modules\elasticsearch\src\lib\connectors\http.js:159:7)  
at IncomingMessage.bound (C:\kibana-6.4.0\node\_modules\elasticsearch\node\_modules\lodash\dist\lodash.js:729:21)  
at emitNone (events.js:111:20)  
at IncomingMessage.emit (events.js:208:7)  
at endReadableNT (\_stream\_readable.js:1064:12)  
at \_combinedTickCallback (internal/process/next\_tick.js:138:11)  
at process.\_tickCallback (internal/process/next\_tick.js:180:9)  
log [06:21:09.820] [warning][stats-collection] Unable to fetch data from kibana\_settings collector

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 21, 2018, 6:56am UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-6-4-with-elasticsearch-6-4/149399/2 "2018-09-21T06:56:21Z")

</div>

Why have you set up the cluster that way? Just because you can have different types of nodes doesn't mean you necessarily should. If your nodes have the same hardware profile, you would most likely be better off setting up all 3 nodes with the default profile (holds data, is master eligible and can handle ingest) as that will spread load and give you better resiliency. Do not forget to set `minimum_master_nodes` according to [these guidelines](https://www.elastic.co/guide/en/elasticsearch/reference/6.4/modules-node.html#split-brain).

---

<div class="post-metadata">

**Author:** ![mrumeshkumar](https://avatars.discourse-cdn.com/v4/letter/m/f9ae1b/32.png) [@mrumeshkumar](https://discuss.elastic.co/u/mrumeshkumar)\
**Post date:** [September 21, 2018, 9:24am UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-6-4-with-elasticsearch-6-4/149399/3 "2018-09-21T09:24:39Z")

</div>

Can you help me providing details how can i utlize all three server for elastic search nodes configuration.  
i had done it 1st time and dont have much idea how to utlize all three servers and setup .and decided lets setup all three nodes separately.

Can you provide any information that can guide me to setup elasticsearch on multiple servers. and how many nodes should i configure on one server. and how to configure them so that all these nodes have cross communication on multipule servers.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 22, 2018, 6:30am UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-6-4-with-elasticsearch-6-4/149399/4 "2018-09-22T06:30:58Z")

</div>

Ideally run one Elasticsearch node per host. Let all nodes have all roles. You can do this by sticking with the defaults and remove `node.data`, `node.ingest`, and `node.master` settings from the elasticsearch.yml files. Update [discovery.zen.ping.unicast.hosts](https://www.elastic.co/guide/en/elasticsearch/reference/6.4/modules-network.html#modules-network) so it contains the IP address of all hosts. Also make sure that `network.host` binds to an interface the other nodes can access. Then set `minimum_master_nodes` to 2 in order to prevent split-brain scenarios.

---

<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:** [October 20, 2018, 6:31am UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-6-4-with-elasticsearch-6-4/149399/5 "2018-10-20T06:31:03Z")

</div>

Closed on October 20, 2018, 6:31am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.