CODEWITHSUNDEEP
elasticsearchkibanakibana-4
Mangoski
Mangoski

Reputation: 2119

Elasticsearch is still initializing the kibana index

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

Upvotes: 55

Views: 57821

Answers (4)

gaellm
gaellm

Reputation: 839

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

Upvotes: 81

Yuvraj Gupta
Yuvraj Gupta

Reputation: 2475

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.

Upvotes: 65

pbaranski
pbaranski

Reputation: 24952

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.

Upvotes: 6

Shlomi Gutman
Shlomi Gutman

Reputation: 29

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.

Upvotes: -2

Related Questions