Elasticsearch(2.3.5) is still initializing the kibana index

Elastic Stack Elasticsearch
1

Elasticsearch version: 2.3.5

**KIbana Version : 4.5.4

Plugins installed: [kopf]

JVM version: 8

OS version: ubuntu 16.04

I recently installed elastic search 2.3.5 and Kibana 4.5.4 on my EC2 instance.

Both services are running. Before installing kibana my ES cluster health was "Green". When i installed latest kibana, it went to "RED".

When i access kibana it says,

Elasticsearch is still initializing the kibana index.

Tried to delete the kibana index and restart kibana server. But still the problem exists.

screen shot 2016-08-06 at 7 23 12 pm
43dfebaa-5c0c-11e6-9b80-ad61734c7f80.png1145×304

below is my ES logs,


[2016-08-06 13:45:06,542][INFO ][node                     ] [elk-v3-es-client-2] initialized
[2016-08-06 13:45:06,542][INFO ][node                     ] [elk-v3-es-client-2] starting ...
[2016-08-06 13:45:06,646][INFO ][transport                ] [elk-v3-es-client-2] publish_address {10.10.25.255:9300}, bound_addresses {0.0.0.0:9300}
[2016-08-06 13:45:06,656][INFO ][discovery                ] [elk-v3-es-client-2] logs-v3/Ay90INLJT8-ztY_K0FMRDg
[2016-08-06 13:45:10,233][INFO ][cluster.service          ] [elk-v3-es-client-2] new_master {elk-v3-es-client-2}{Ay90INLJT8-ztY_K0FMRDg}{10.10.25.255}{10.10.25.255:9300}{max_local_storage_nodes=1, data=f$
[2016-08-06 13:45:10,284][INFO ][http                     ] [elk-v3-es-client-2] publish_address {10.10.25.255:9200}, bound_addresses {0.0.0.0:9200}
[2016-08-06 13:45:10,284][INFO ][node                     ] [elk-v3-es-client-2] started
[2016-08-06 13:45:10,297][INFO ][gateway                  ] [elk-v3-es-client-2] recovered [1] indices into cluster_state
[2016-08-06 13:49:56,450][INFO ][node                     ] [elk-v3-es-client-2] stopping ...
[2016-08-06 13:49:56,471][INFO ][node                     ] [elk-v3-es-client-2] stopped
[2016-08-06 13:49:56,471][INFO ][node                     ] [elk-v3-es-client-2] closing ...
[2016-08-06 13:49:56,477][INFO ][node                     ] [elk-v3-es-client-2] closed
[2016-08-06 13:49:57,263][INFO ][node                     ] [elk-v3-es-client-2] version[2.3.5], pid[20892], build[90f439f/2016-07-27T10:36:52Z]
[2016-08-06 13:49:57,265][INFO ][node                     ] [elk-v3-es-client-2] initializing ...
[2016-08-06 13:49:58,218][INFO ][plugins                  ] [elk-v3-es-client-2] modules [reindex, lang-expression, lang-groovy], plugins [cloud-aws, kopf], sites [kopf]
[2016-08-06 13:49:58,248][INFO ][env                      ] [elk-v3-es-client-2] using [1] data paths, mounts [[/ (/dev/xvda1)]], net usable_space [45.3gb], net total_space [49gb], spins? [no], types [ex$
[2016-08-06 13:49:58,248][INFO ][env                      ] [elk-v3-es-client-2] heap size [3.8gb], compressed ordinary object pointers [true]
[2016-08-06 13:49:58,248][WARN ][env                      ] [elk-v3-es-client-2] max file descriptors [65535] for elasticsearch process likely too low, consider increasing to at least [65536]
[2016-08-06 13:50:01,128][INFO ][node                     ] [elk-v3-es-client-2] initialized
[2016-08-06 13:50:01,128][INFO ][node                     ] [elk-v3-es-client-2] starting ...
[2016-08-06 13:50:01,227][INFO ][transport                ] [elk-v3-es-client-2] publish_address {10.10.25.255:9300}, bound_addresses {0.0.0.0:9300}
[2016-08-06 13:50:01,235][INFO ][discovery                ] [elk-v3-es-client-2] logs-v3/Jr9Fh64kQ9-4AfimOD7KjQ
[2016-08-06 13:50:04,875][INFO ][cluster.service          ] [elk-v3-es-client-2] new_master {elk-v3-es-client-2}{Jr9Fh64kQ9-4AfimOD7KjQ}{10.10.25.255}{10.10.25.255:9300}{max_local_storage_nodes=1, data=f$
[2016-08-06 13:50:04,919][INFO ][http                     ] [elk-v3-es-client-2] publish_address {10.10.25.255:9200}, bound_addresses {0.0.0.0:9200}
[2016-08-06 13:50:04,920][INFO ][node                     ] [elk-v3-es-client-2] started
[2016-08-06 13:50:04,940][INFO ][gateway                  ] [elk-v3-es-client-2] recovered [1] indices into cluster_state

helps would be appreciated

2

What does _cat/indices show?

3

@warkolm

it says's

red open .kibana 1 1
One thing i found is , the current ES node is a client node(Where i set node.master = true and node.data = false, http.enable = true). If i remove these settings Kibana works fine. Any idea why this happens?

4

Yeah, you are telling that node it cannot store data. And unless you have other nodes in the cluster then that index with it's data can never be allocated.

5

Ooops what an idiot I am. :slight_smile: Thanks alot @warkolm