# Kibana not work, after elasticsearch cluster is red **URL:** \ **Category:** Kibana\ **Created:** [October 27, 2018, 8:14am UTC](https://discuss.elastic.co/t/kibana-not-work-after-elasticsearch-cluster-is-red/154277 "2018-10-27T08:14:24Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jsyu32](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@jsyu32](https://discuss.elastic.co/u/jsyu32)\ **Post date:** [October 27, 2018, 8:14am UTC](https://discuss.elastic.co/t/kibana-not-work-after-elasticsearch-cluster-is-red/154277/1 "2018-10-27T08:14:25Z")
2 of 3 data nodes are down. The cluster turns red, and kibana doesn't work. How to fix it? ![WX20181027-161012%402x](https://us1.discourse-cdn.com/elastic/original/3X/b/5/b5669e811f579a71bb5071462febe333c5fde660.png) ![WX20181027-161115%402x](https://us1.discourse-cdn.com/elastic/original/3X/2/b/2bd511c06a8a6c22c17e527c0f093b1e01627eb0.png) ![WX20181027-161148%402x](https://us1.discourse-cdn.com/elastic/original/3X/5/8/58fce9173c5aa600bf97d384efec36d04d31022c.png) ---
**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\ **Post date:** [October 29, 2018, 3:02pm UTC](https://discuss.elastic.co/t/kibana-not-work-after-elasticsearch-cluster-is-red/154277/2 "2018-10-29T15:02:00Z")
Hi, What does your Kibana logs say? Did you try restarting Kibana? Also which node is Kibana connected to? Is it connected to the 2 of those nodes which are down? Thanks. Bhavya ---
**Author:** ![jsyu32](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@jsyu32](https://discuss.elastic.co/u/jsyu32)\ **Post date:** [October 30, 2018, 3:09am UTC](https://discuss.elastic.co/t/kibana-not-work-after-elasticsearch-cluster-is-red/154277/3 "2018-10-30T03:09:05Z")
I guess it is due to .kibana index lost {"type":"error","@timestamp":"2018-10-28T20:44:27Z","tags":["warning","monitoring-ui","kibana-monitoring"],"pid":1260,"level":"error","error":{"message":"[no\_shard\_available\_action\_exception] No shard available f or [get [.kibana][doc][config:6.3.0]: routing [null]]","name":"Error","stack":"[no\_shard\_available\_action\_exception] No shard available for [get [.kibana][doc][config:6.3.0]: routing [null]] :: {"path":"/.kiba na/doc/config%3A6.3.0","query":{},"statusCode":503,"response":"{\"error\":{\"root\_cause\":[{\"type\":\"no\_shard\_available\_action\_exception\",\"reason\":\"No shard available for [get [.kibana][doc][config:6.3.0]: routing [null]]\"}],\"type\":\"no\_shard\_available\_action\_exception\",\"reason\":\"No shard available for [get [.kibana][doc][config:6.3.0]: routing [null]]\"},\"s tatus\":503}"}\n at respond (/home/pp\_risk\_rom\_batch/kibana-6.3.0-linux-x86\_64/node\_modules/elasticsearch/src/lib/transport.js:307:15)\n at checkRespForFailure (/home/pp\_risk\_rom\_batch/kibana-6.3.0-linux -x86\_64/node\_modules/elasticsearch/src/lib/transport.js:266:7)\n at HttpConnector. (/home/pp\_risk\_rom\_batch/kibana-6.3.0-linux-x86\_64/node\_modules/elasticsearch/src/lib/connectors/http.js:159:7)\n at IncomingMessage.bound (/home/pp\_risk\_rom\_batch/kibana-6.3.0-linux-x86\_64/node\_modules/elasticsearch/node\_modules/lodash/dist/lodash.js:729:21)\n at emitNone (events.js:111:20)\n at IncomingMessage.emit (events.js:208:7)\n at endReadableNT (\_stream\_readable.js:1064:12)\n at \_combinedTickCallback (internal/process/next\_tick.js:138:11)\n at process.\_tickDomainCallback (internal/process/next\_tick.js:218:9 )"},"message":"[no\_shard\_available\_action\_exception] No shard available for [get [.kibana][doc][config:6.3.0]: routing [null]]"} {"type":"log","@timestamp":"2018-10-28T20:44:27Z","tags":["warning","monitoring-ui","kibana-monitoring"],"pid":1260,"message":"Unable to fetch data from kibana\_settings collector"} {"type":"error","@timestamp":"2018-10-28T20:44:37Z","tags":["warning","monitoring-ui","kibana-monitoring"],"pid":1260,"level":"error","error":{"message":"[search\_phase\_execution\_exception] all shards failed","nam e":"Error","stack":"[search\_phase\_execution\_exception] all shards failed :: {"path":"/.kibana/\_search","query":{"ignore\_unavailable":true,"filter\_path":"aggregations.types.buckets"},"body":"{\"si ze\":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 sha rds failed\",\"phase\":\"query\",\"grouped\":true,\"failed\_shards\":[]},\"status\":503}"}\n at respond (/home/pp\_risk\_rom\_batch/kibana-6.3.0-linux-x86\_64/node\_modules/elasticsearch/src/l ib/transport.js:307:15)\n at checkRespForFailure (/home/pp\_risk\_rom\_batch/kibana-6.3.0-linux-x86\_64/node\_modules/elasticsearch/src/lib/transport.js:266:7)\n at HttpConnector. (/home/pp\_risk\_rom\_b atch/kibana-6.3.0-linux-x86\_64/node\_modules/elasticsearch/src/lib/connectors/http.js:159:7)\n at IncomingMessage.bound (/home/pp\_risk\_rom\_batch/kibana-6.3.0-linux-x86\_64/node\_modules/elasticsearch/node\_modules /lodash/dist/lodash.js:729:21)\n at emitNone (events.js:111:20)\n at IncomingMessage.emit (events.js:208:7)\n ---
**Author:** ![jsyu32](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@jsyu32](https://discuss.elastic.co/u/jsyu32)\ **Post date:** [October 30, 2018, 4:17am UTC](https://discuss.elastic.co/t/kibana-not-work-after-elasticsearch-cluster-is-red/154277/4 "2018-10-30T04:17:43Z")
I delete the .kibana index. And run kibana again. It is normal now. However the charts, index pattern are all lost. Does it mean all kibana related settings/ configs/ charts/ index patterns are stored in .kibana index? Thanks ---
**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\ **Post date:** [October 30, 2018, 1:06pm UTC](https://discuss.elastic.co/t/kibana-not-work-after-elasticsearch-cluster-is-red/154277/5 "2018-10-30T13:06:26Z")
Yes they are. We usually ask our users to take a snapshot of the data or export all saved objects before doing any delete operations. Hope this helps you? 🙂 Thanks, Bhavya ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 27, 2018, 1:06pm UTC](https://discuss.elastic.co/t/kibana-not-work-after-elasticsearch-cluster-is-red/154277/6 "2018-11-27T13:06:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.