Elasticsearch is still initializing the kibana index

Question

When I am trying to start Kibana I am facing the following issue. I first restarted my elasticsearch server it was running successfully. After starting Elasticsearch I tried to start Kibana but no luck.

{"name":"Kibana","hostname":"ABCD","pid":3848,"level":30,"msg":"Elasticsearch is still initializing the kibana index... Trying again in 2.5 second.","time":"2015-07-03T07:35:34.936Z","v":0}

Thanks in advance

score 81 · Answer 1 · edited Jan 17 '22 at 17:59

81

the curl -XDELETE http://localhost:9200/.kibana command works fine, however you lose all your Kibana settings (indexes, graphs, dashboards); by just querying the index I've solved the problem, without losing my data. For example:

curl -s http://localhost:9200/.kibana/_recovery?pretty
curl -XPUT 'localhost:9200/.kibana/_settings' -d '
{
    "index" : {
        "number_of_replicas" : 0
    }
}'

Then start Kibana, it should work.

Gael Le Moellic

edited Jan 17 '22 at 17:59

g t

7,287
7
50
85

answered Feb 25 '16 at 16:38

gaellm

851
6
4

1

I only ran the first curl statement and it worked for me. No idea why. Would love an explanation/more details if possible. – rabidang3ls Feb 05 '18 at 23:05
3

with ES 6 and above, you'll probably need to add `-H 'Content-Type: application/json'` to the second curl command -- [see the announcement](https://www.elastic.co/blog/strict-content-type-checking-for-elasticsearch-rest-requests) – a different ben Mar 13 '18 at 06:51
life safer, just the first curl request works if you deleted your .kibana index, works also on opensearch – Antonio Terreno Jun 29 '22 at 12:31

score 65 · Accepted Answer · edited Sep 18 '17 at 17:06

65

Warning: Removing .kibana index will make you lose all your kibana settings (indexes, graphs, dashboards)

This behavior is sometimes caused by an existing .kibana index. Kindly delete the .kibana index in elasticsearch using following command:

curl -XDELETE http://localhost:9200/.kibana

After deleting the index, restart Kibana.

If the problem still persists, and you are willing to lose any existing data, you can try deleting all indexes using following command:

curl -XDELETE http://localhost:9200/*

Followed by restarting Kibana.

Note: localhost:9200 is the elasticsearch server's host:port, which may be different in your case.

edited Sep 18 '17 at 17:06

FluxLemur

1,827
16
18

answered Jul 08 '15 at 10:09

Yuvraj Gupta

2,475
16
26

1

Yes I did the same procedure now its working now. I don't why index was crashing. Any how thanks for the help dude. – Mangoski Jul 08 '15 at 11:32
Where is this .kibana stored? – sliders_alpha Oct 21 '15 at 09:21
It is stored inside elasticsearch-version/data/clustername/nodes/nodeno/indices folder. – Yuvraj Gupta Oct 22 '15 at 10:43
5

Please also note @gaellm 's answer below which does *NOT* require deleting the index. – Blachshma Jun 19 '16 at 08:46
1

Everything is lost after DELETE indexes...that's an important sideoff effect :S – mcarra66 Jul 05 '17 at 09:44
3

This answer should not be the correct one @Mangoski, as it is destructive. The answer provided below is non-destructive and is the correct one. – Pedro Mata-Mouros Aug 23 '17 at 16:30
1

Downvoted, because @gaellm 's answer should work in most cases. That should always be tried first. Deleting the index is only a last resort solution even if you have hot backups. – Sobvan Sep 28 '17 at 09:11
I got a bad gateway error after this. But it worked once I restarted all of the elk services. – Abhishek J Aug 16 '18 at 06:11

score 6 · Answer 3 · answered Jan 04 '17 at 08:45

6

Sometimes you need to wait few minutes after restarting ES.
That can be also connected with low disk space.
Observed on AWS t2.small machine with ELK stack.

answered Jan 04 '17 at 08:45

pbaranski

22,778
19
100
117

What would be a few minutes? 5? 15? 30? Not trying to be mean, but just want to know what 'normal' is. – CBBSpike Jan 24 '18 at 15:02
Rough below 10min for t2.small and 50GB of data in ES. Depends from to many factors to estimate :) – pbaranski Jan 25 '18 at 13:13

score -2 · Answer 4 · edited Jul 06 '15 at 21:47

-2

Something is wrong with your Kibana index inside elasticsearch. I had the same message and i just deleted my Kibana index and then, when i restarted it, a new index of Kibana was created by the service.

edited Jul 06 '15 at 21:47

lenz

5,658
5
24
44

answered Jul 06 '15 at 21:11

Shlomi Gutman

29
3

Elasticsearch is still initializing the kibana index

4 Answers4

Linked