# Elasticsearch is still initializing the kibana index (please help) **URL:** \ **Category:** Elasticsearch\ **Created:** [June 1, 2016, 9:29am UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535 "2016-06-01T09:29:49Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Python\_Coder](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Python\_Coder](https://discuss.elastic.co/u/Python_Coder)\ **Post date:** [June 1, 2016, 9:29am UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/1 "2016-06-01T09:29:49Z")
Please help, i have an ES cluster with ES v2.3.3, but after installing kibana, i got this error and kibana displays statistics only Error: > plugin:elasticsearch: Elasticsearch is still initializing the kibana index. ---
**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\ **Post date:** [June 1, 2016, 9:45am UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/2 "2016-06-01T09:45:44Z")
Which version of kibana are you using? What do the Elasticsearch logs tell you? ---
**Author:** ![Python\_Coder](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Python\_Coder](https://discuss.elastic.co/u/Python_Coder)\ **Post date:** [June 1, 2016, 10:18am UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/3 "2016-06-01T10:18:53Z")
I'm using Kibana 4.5.1 ElasticSearch cluster works fine, and everything is good, and after refreshing the kibana webpage, nothing added to the log file. Thanks for your answer 🙂 ---
**Author:** ![Python\_Coder](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Python\_Coder](https://discuss.elastic.co/u/Python_Coder)\ **Post date:** [June 1, 2016, 10:41am UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/4 "2016-06-01T10:41:58Z")
I'm sorry, ES seems to have a problem. > [root@LS1 ~]# curl -s [http://localhost:9200/\_cluster/health?pretty](http://localhost:9200/_cluster/health?pretty) > { > "cluster\_name" : "ESCLUSTER", > "status" : "red", > "timed\_out" : false, > "number\_of\_nodes" : 2, > "number\_of\_data\_nodes" : 2, > "active\_primary\_shards" : 6, > "active\_shards" : 12, > "relocating\_shards" : 0, > "initializing\_shards" : 0, > "unassigned\_shards" : 9, > "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" : 57.14285714285714 > } ---
**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\ **Post date:** [June 1, 2016, 2:10pm UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/5 "2016-06-01T14:10:23Z")
Red cluster state indicated that there is at least one primary shard missing for one index. How many indices and how many shards per index are you expecting in your cluster setup? What does > curl -s [http://localhost:9200/\_settings](http://localhost:9200/_settings) and > curl -s [http://localhost:9200/\_cat/shards?v](http://localhost:9200/_cat/shards?v) Also it would be helpful to know if you are starting from a fresh install or if you changed any of the settings before installing kibana. ---
**Author:** ![Python\_Coder](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Python\_Coder](https://discuss.elastic.co/u/Python_Coder)\ **Post date:** [June 1, 2016, 2:33pm UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/6 "2016-06-01T14:33:20Z")
SETTINGS OUTPUT: > { > ".kibana" : { > "settings" : { > "index" : { > "creation\_date" : "1464778671213", > "number\_of\_shards" : "1", > "number\_of\_replicas" : "2", > "uuid" : "rDda9hR2SiSVIRhGmUmh1w", > "version" : { > "created" : "2030399" > } > } > } > }, > "logstash-ossec-2016.06.01" : { > "settings" : { > "index" : { > "creation\_date" : "1464788269166", > "refresh\_interval" : "5s", > "number\_of\_shards" : "6", > "number\_of\_replicas" : "2", > "uuid" : "rm06bX2iSDqDqjt-CXLHkA", > "version" : { > "created" : "2030399" > } > } > } > } > } CAT SHARDS OUTPUT: > index shard prirep state docs store ip node > .kibana 0 r STARTED 2 11.6kb 172.16.122.208 ES2 > .kibana 0 p STARTED 2 11.6kb 172.16.122.207 ES1 > .kibana 0 r UNASSIGNED > logstash-ossec-2016.06.01 2 r STARTED 368 943.6kb 172.16.122.208 ES2 > logstash-ossec-2016.06.01 2 p STARTED 368 863.9kb 172.16.122.207 ES1 > logstash-ossec-2016.06.01 2 r UNASSIGNED > logstash-ossec-2016.06.01 5 r STARTED 370 979kb 172.16.122.208 ES2 > logstash-ossec-2016.06.01 5 p STARTED 370 979kb 172.16.122.207 ES1 > logstash-ossec-2016.06.01 5 r UNASSIGNED > logstash-ossec-2016.06.01 1 r STARTED 381 846.7kb 172.16.122.208 ES2 > logstash-ossec-2016.06.01 1 p STARTED 381 922.9kb 172.16.122.207 ES1 > logstash-ossec-2016.06.01 1 r UNASSIGNED > logstash-ossec-2016.06.01 3 r STARTED 383 1mb 172.16.122.208 ES2 > logstash-ossec-2016.06.01 3 p STARTED 383 973.2kb 172.16.122.207 ES1 > logstash-ossec-2016.06.01 3 r UNASSIGNED > logstash-ossec-2016.06.01 4 r STARTED 400 882.9kb 172.16.122.208 ES2 > logstash-ossec-2016.06.01 4 p STARTED 400 1.5mb 172.16.122.207 ES1 > logstash-ossec-2016.06.01 4 r UNASSIGNED > logstash-ossec-2016.06.01 0 r STARTED 364 986.5kb 172.16.122.208 ES2 > logstash-ossec-2016.06.01 0 p STARTED 364 1mb 172.16.122.207 ES1 > logstash-ossec-2016.06.01 0 r UNASSIGNED Now Cluster state is yallow and unassigned\_shards is 7 > "unassigned\_shards" : 7, ---
**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:** [June 1, 2016, 2:38pm UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/7 "2016-06-01T14:38:39Z")
As you only have 2 data nodes, Elasticsearch will only be able to assign one replica. Either change the `number_of_replicas` setting to 1 or add an additional data node. Elasticsearch will not assign multiple copies of the same shard to the same node. ---
**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\ **Post date:** [June 1, 2016, 2:45pm UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/8 "2016-06-01T14:45:44Z")
This looks like Kibana should be able to start now, though? Still having problems there? ---
**Author:** ![Python\_Coder](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Python\_Coder](https://discuss.elastic.co/u/Python_Coder)\ **Post date:** [June 1, 2016, 2:50pm UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/9 "2016-06-01T14:50:00Z")
I'm running ES as a service, how can i start multiple nodes there? and yes cbuescher, kibana has started now, but ES status is yellow ---
**Author:** ![cbuescher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cbuescher/32/60402_2.png) [@cbuescher](https://discuss.elastic.co/u/cbuescher)\ **Post date:** [June 1, 2016, 3:05pm UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/10 "2016-06-01T15:05:06Z")
Yellow is to be expected when you want 2 replicas but only have 2 nodes, as @Christian_Dahlqvist already pointed out. Where are you running ES as a service? If it is Elastic Cloud, you will get help at their forum at [https://discuss.elastic.co/c/cloud](https://discuss.elastic.co/c/cloud) ---
**Author:** ![Python\_Coder](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Python\_Coder](https://discuss.elastic.co/u/Python_Coder)\ **Post date:** [June 1, 2016, 3:24pm UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/11 "2016-06-01T15:24:47Z")
No, i meant a normal system service, i have 4 physical servers with elk installed including redis and pacemaker for HA, however, do you suggest any solution to start multiple nodes? in my case i start ES using an LSB script exists within the /etc/init.d/ dir. thanks ---
**Author:** ![seth.yes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seth.yes/32/11788_2.png) [@seth.yes](https://discuss.elastic.co/u/seth.yes)\ **Post date:** [October 24, 2016, 3:44pm UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/12 "2016-10-24T15:44:36Z")
I had this same issue, install other Kibana plugins, reinstall ES (as mentioned in other threads) didn't fix it. I ended up having to rename my single-node cluster (just appended a '1' to the end) and it fired right up. Kibana: 4.6.1 ES: 2.4.1 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:10pm UTC](https://discuss.elastic.co/t/elasticsearch-is-still-initializing-the-kibana-index-please-help/51535/13 "2017-07-05T22:10:11Z")