Kibana: Readiness probe failed: HTTP probe failed with statuscode: 503

Hi All,

I have created Elasticsearch/kibana using eck operator. Although kibana pod is running, I see that readiness probe is failed i.e Readiness probe failed: HTTP probe failed with statuscode: 503. What could be reason for this? How can I over come this.

Kibana pod logs as follow:

{"type":"log","@timestamp":"2021-10-12T12:43:55Z","tags":["warning","Elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: https://testing-es-http.elastic-clusters.svc:9200/"}

{"type":"log","@timestamp":"2021-10-12T12:43:55Z","tags":["warning","Elasticsearch","admin"],"pid":1,"message":"No living connections"}

I am unable to access kibana webUI not sure whether the above warning is causing it.

1 Like

Hi @purushothamkdr143, thanks for your question.

Can you provide a little bit more information? Elasticsearch logs, more Kibana logs, ECK operator logs and both Elasticsearch/Kibana resource manifests would be very useful to investigate further. You can capture all these information either manually or by using our diagnostic tool and share this information in this thread or, more privately, via eck@elastic.co.

Thanks,
David

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