Elasticsearch is still initializing the kibana index (please help)

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


plugin:elasticsearch: Elasticsearch is still initializing the kibana index.

Which version of kibana are you using? What do the Elasticsearch logs tell you?

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 :slight_smile:

I'm sorry, ES seems to have a problem.

[root@LS1 ~]# curl -s 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

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


curl -s 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.


".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"


index shard prirep state docs store ip node
.kibana 0 r STARTED 2 11.6kb ES2
.kibana 0 p STARTED 2 11.6kb ES1
.kibana 0 r UNASSIGNED
logstash-ossec-2016.06.01 2 r STARTED 368 943.6kb ES2
logstash-ossec-2016.06.01 2 p STARTED 368 863.9kb ES1
logstash-ossec-2016.06.01 2 r UNASSIGNED
logstash-ossec-2016.06.01 5 r STARTED 370 979kb ES2
logstash-ossec-2016.06.01 5 p STARTED 370 979kb ES1
logstash-ossec-2016.06.01 5 r UNASSIGNED
logstash-ossec-2016.06.01 1 r STARTED 381 846.7kb ES2
logstash-ossec-2016.06.01 1 p STARTED 381 922.9kb ES1
logstash-ossec-2016.06.01 1 r UNASSIGNED
logstash-ossec-2016.06.01 3 r STARTED 383 1mb ES2
logstash-ossec-2016.06.01 3 p STARTED 383 973.2kb ES1
logstash-ossec-2016.06.01 3 r UNASSIGNED
logstash-ossec-2016.06.01 4 r STARTED 400 882.9kb ES2
logstash-ossec-2016.06.01 4 p STARTED 400 1.5mb ES1
logstash-ossec-2016.06.01 4 r UNASSIGNED
logstash-ossec-2016.06.01 0 r STARTED 364 986.5kb ES2
logstash-ossec-2016.06.01 0 p STARTED 364 1mb ES1
logstash-ossec-2016.06.01 0 r UNASSIGNED

Now Cluster state is yallow and unassigned_shards is 7

"unassigned_shards" : 7,

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.

This looks like Kibana should be able to start now, though? Still having problems there?

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

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

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.

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