GoogleCloudPlatform / GoogleCloudPlatform/click-to-deploy
Kibana stuck at kibana-waiter state. Unable to revive connection: http://elasticsearch:9200/"}
- Dominant language
- Python
- Stars
- 773
- Forks
- 465
- Avg merge
- 5h 52m
- Merged PRs (30d)
- 8
Description
**Category:**
elastic-gke-logging
Kubernetes apps
Description
I am trying to deploy "elastic-gke-logging" on GKE, Elasticsearch and fluentd is working but kibana and kibana init job are facing issue as mentioned below. I am using following tag for all images.
gcr.io/cloud-marketplace/google/elastic-gke-logging/kibana:`6.8.13-20210321-144920`
```
{"type":"log","@timestamp":"2021-11-29T17:17:44Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
{"type":"log","@timestamp":"2021-11-29T17:17:44Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
```
NAME READY STATUS RESTARTS AGE
efk-elasticsearch-0 2/2 Running 0 75m
efk-elasticsearch-1 2/2 Running 0 74m
efk-fluentd-es-5qm4c 1/1 Running 0 75m
efk-fluentd-es-lhhjb 1/1 Running 0 75m
efk-fluentd-es-z9xsg 1/1 Running 0 75m
```
efk-kibana-c4f94675d-vf48n 0/1 Running 10 32m
efk-kibana-init-job-c2d54 0/1 Init:0/1 0 32m
```
Please help regarding this issue.
Contributor guide
Research direction
Start with the reported Kibana logs, pod statuses, and the http://elasticsearch:9200/ endpoint in the GKE deployment. Trace why the Kibana pod and init job cannot establish a living Elasticsearch connection. Done means Kibana connects successfully and the init job completes instead of remaining stuck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, gcp, kubernetes
- Domain
- cloud, devops, infrastructure, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100