Kibana server is not ready yet

Elastic Stack Kibana
1

Hello there , I need help

I am getting Error : Kibana server is not ready yet . When I check my Kibana.yml logs . I get this:

{"type":"log","@timestamp":"2021-09-21T19:59:32+03:00","tags":["error","savedobjects-service"],"pid":1832,"message":"[.kibana_task_manager] Action failed with 'Request timed out'. Retrying attempt 4 in 16 seconds."}
{"type":"log","@timestamp":"2021-09-21T19:59:32+03:00","tags":["info","savedobjects-service"],"pid":1832,"message":"[.kibana_task_manager] INIT -> INIT. took: 38006ms."}

My Kibana.yml

server.port: 5601
server.host: "0.0.0.0"
elasticsearch.hosts: ["http://0.0.0.0:9200"]

My elasticsearch.yml

network.host: 0.0.0.0
http.port: 9200
cluster.initial_master_nodes: node-1


curl 0.0.0.0:5601
Kibana server is not ready yet

 curl 0.0.0.0:9200     
{
  "name" : "kali",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "_na_",
  "version" : {
    "number" : "7.14.1",
    "build_flavor" : "default",
    "build_type" : "deb",
    "build_hash" : "66b55ebfa59c92c15db3f69a335d500018b3331e",
    "build_date" : "2021-08-26T09:01:05.390870785Z",
    "build_snapshot" : false,
    "lucene_version" : "8.9.0",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"

What could be the problem ?

2

Is this a new installation or an upgrade ?

Are both on the same server ?

It could be it is timing out migrating the saved_0bjects (if Upgrade)

4

After new installation it gave me the same error , then I upgraded Kibana . I still got the same error

5

This looks to me more that your kibana data in elasticsearch needs to be removed (if possible for you). Re-installing Kibana won't do much if the indices from the failed installation still reside in elasticsearch.

There are various ways to remove those indices from your elasticsearch data

7

Like this ?

curl -X DELETE 'http://0.0.0.0:9200/_all'
8

just try first the kibana indices... maybe this or with a wildcard

curl -XDELETE http://0.0.0.0:9200/.kibana
1 Like
9

running

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

I got his error;

`{`
`  "error" : {`
`    "root_cause" : [`
`      {`
`        "type" : "master_not_discovered_exception",`
`        "reason" : null`
`      }`
`    ],`
`    "type" : "master_not_discovered_exception",`
`    "reason" : null`
`  },`
`  "status" : 503`
`}`

I figured , it also has to do with cluster id being being null ;

"cluster_uuid" : "_na_",

I fixed it by adding ;

node.name: my node
cluster.initial_master_nodes: ["my node"]

Found the solution on stack overflow; https://stackoverflow.com/questions/67451816/elasticsearch-issue-with-cluster-uuid-na-and-license-in-null

Thank you for your assistance.

1 Like
10

Good catch

11

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.