Kibana server is not ready yet

[AlexIch]

HI guys
Im getting Kibana server is not ready yet error when Opening Kibana dashboard

Elasticsearch.yml:
cluster.name: xiake-els-server
node.name: node-1
path.data: /data/Elasticsearch/data
path.logs: /data/Elasticsearch/log
network.host: 10.112.5.3
#discovery.seed_hosts: ["10.112.5.3", "10.112.5.5"]
discovery.seed_providers: file
cluster.initial_master_nodes: ["node-1","node-2"]
bootstrap.memory_lock: true
cluster.max_shards_per_node: 20000

kibana.yml:
server.host: "0.0.0.0"
Elasticsearch.hosts: ["http://10.112.5.3:9200"]
monitoring.kibana.collection.enabled: false

try to follow the instructions in Error "Kibana server is not ready yet"
but unfortunately, I can't see any index called kibana there to remove.

Appreciate your support to fix this issue

[zx8086]

Hi @AlexIch, welcome !

Is this after a fresh installation or an upgrade ?

What does it say in the kibana logs ?

[AlexIch]

it‘s a fresh installation
kibana start log from journalctl -xe:

"message":"Unable to connect to Elasticsearch. Error: [resource_already_exists_exception] index [.kibana_1/3tHHjMYzS8aEqB2Zi5v7eQ] already exists, with { index_uuid="3tHHjMYzS8aEqB2Zi5v7eQ" & index [.kibana_1/3tHHjMYzS8aEqB2Zi5v7eQ] already exists, with { index_uuid="3tHHjMYzS8aEqB2Zi5v7eQ" & index=".kibana_1" }"}
"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."}
"message":"Unable to connect to Elasticsearch. Error: [resource_already_exists_exception] index [.kibana_task_manager_1/fLghxb93S7S6fFNdeaNDVw] already exists, with { index_uuid="fLghxb93S7S6fFNd already exists, with { index_uuid="3tHHjMYzS8aEqB2Zi5v7eQ" & index [.kibana_task_manager_1/fLghxb93S7S6fFNdeaNDVw] already exists, with { index_uuid="fLghxb93S7S6fFNdeaNDVw" & index=".kibana_task_manager_1" }"}

I don't understand del index called '.kibana_task_manager_1' and '.kibana_1'

[AlexIch]

[root@iZuf6132wo6qz9tep7m3bwZ Elasticsearch]# curl -XGET http://10.112.5.3:9200/
{
"name" : "node-1",
"cluster_name" : "xiake-els-server",
"cluster_uuid" : "F00-Md83RCCQz1UPvGQ0hg",
"version" : {
"number" : "7.8.0",
"build_flavor" : "default",
"build_type" : "rpm",
"build_hash" : "757314695644ea9a1dc2fecd26d1a43856725e65",
"build_date" : "2020-06-14T19:35:50.234439Z",
"build_snapshot" : false,
"lucene_version" : "8.5.1",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}

[zx8086]

It looks like the fresh installation was still installing whilst another instance was launched.

Kibana needs time to start and build up it's initial indexes... try killing all instances, starting kibana again and waiting via the logs when it indicates Kibana is Available

[AlexIch]

how long did kibana needs time ?
what should I do now？wait for it starting ?
please help
thx

[AlexIch]

[zx8086]

I have seen it take more that 20 - 30 minutes depending on your hardware.... if after a while you might need to delete that index. if it is a fresh installation you lose nothing.