Tag Archives: Kibana

Kibana Connect Error: Kibana server is not ready yet [How to Solve]

Problem description

An error occurs when the browser connects to kibana

Kibana server is not ready yet

View kibana log

{"type":"log","@timestamp":"2021-11-29T02:45:50Z","tags":["warning","elasticsearch","admin"],"pid":8,"message":"Unable to revive connection: http://120.79.137.87:9200/"}

reason

Check whether the configuration of kibana container startup is consistent with the following

docker run --name kibana \
-e ELASTICSEARCH_HOSTS=http://120.79.137.87:9200/ \
-p 5601:5601 \
-d kibana:7.6.2

In case of inconsistency, stop the container, delete it, and create a new kibana container again

Then kibana was started and an error was reported

{"type":"log","@timestamp":"2021-11-29T02:53:35Z","tags":["warning","savedobjects-service"],"pid":7,"message":"Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana_1 and restarting Kibana."}

Solution

Stop the kibana service, and then delete the four indexes from elasticsearch

curl -XDELETE http://IP:9200/.kibana
curl -XDELETE http://IP:9200/.kibana*
curl -XDELETE http://IP:9200/.kibana_2
curl -XDELETE http://IP:9200/.kibana_1

Solution of kibana starting error reporting server is not ready yet

Open source software supply chain lighting plan, waiting for you>>>

Preface:

Today, when building elasticsearch cluster, we report the problem of kibana server is not ready yet when using kibana to operate elasticsearch again

Through searching for information on the Internet, most of them say that the versions of kibana and elastic search are inconsistent, but I can use them normally before building a cluster

My kibana and elastic search are both installed through homebrew, and both versions should be consistent. Later found a solution, hereby record

Exception details:

"warning","migrations","pid":6181,"message":"Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana_index_1 and restarting Kibana.

The main message is this warning, prompting. Kibana_ index_ 1 file, and restart kibana, then follow the steps below

Stop kibana 1

service kibana stop

Delete kibana index 2

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

Start kibana 3

service kibana start

Summary

Be sure to read the log information carefully and don’t ignore the warning. It’s over