Course: Elastic Observability Engineer On-Demand
Version: 8.2.0
Question: After completing module 7, pausing the lab, and then returning to begin module 8, I'm receiving a 'Kibana server is not ready yet.' error.
I've tried restarting the machines using the gear icon on the lab itself and restarting the kibana and elasticsearch docker containers with no change. Checking the health of the kibana container shows multiple 503s, though I can't tell what its checking that's returning those:
elastic@ip-172-31-8-179:~/elastic-agent-8.8.2-linux-x86_64$ docker inspect --format "{{json .State.Health }}" kibana | jq
{
"Status": "unhealthy",
"FailingStreak": 68,
"Log": [
{
"Start": "2025-07-10T19:36:09.849799381Z",
"End": "2025-07-10T19:36:09.923285275Z",
"ExitCode": 22,
"Output": "HTTP 503"
},
{
"Start": "2025-07-10T19:36:19.924276344Z",
"End": "2025-07-10T19:36:19.989855255Z",
"ExitCode": 22,
"Output": "HTTP 503"
},
{
"Start": "2025-07-10T19:36:29.99065337Z",
"End": "2025-07-10T19:36:30.057688585Z",
"ExitCode": 22,
"Output": "HTTP 503"
},
{
"Start": "2025-07-10T19:36:40.059089268Z",
"End": "2025-07-10T19:36:40.13690337Z",
"ExitCode": 22,
"Output": "HTTP 503"
},
{
"Start": "2025-07-10T19:36:50.138575063Z",
"End": "2025-07-10T19:36:50.206286742Z",
"ExitCode": 22,
"Output": "HTTP 503"
}
]
}
All of the other containers appear healthy:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
83ef7efa2a53 training/client-loadgen "dumb-init -- node_m…" 14 months ago Up 36 minutes loadgen
6b1ff5c9eca4 ubuntu_petclinic-client "/root/startup.sh" 14 months ago Up 36 minutes (healthy) 0.0.0.0:4000->4000/tcp, 22/tcp, 0.0.0.0:8080->8080/tcp petclinic-client
dd8c4660ad34 ubuntu_petclinic-server "/root/startup.sh" 14 months ago Up 36 minutes (healthy) 22/tcp, 0.0.0.0:8000->8000/tcp, :::8000->8000/tcp petclinic-server
407d0124367a ubuntu_mysql "/root/startup.sh" 14 months ago Up 36 minutes (healthy) 22/tcp, 0.0.0.0:3306->3306/tcp, :::3306->3306/tcp mysql
466f733beec3 ubuntu_address-finder "/usr/local/bin/guni…" 14 months ago Up 36 minutes (healthy) 0.0.0.0:5000->5000/tcp address-finder
c965fb887e5b docker.elastic.co/beats/elastic-agent-complete:8.8.2 "/usr/bin/tini -- /u…" 14 months ago Up 35 minutes (healthy) 0.0.0.0:8200->8200/tcp, :::8200->8200/tcp, 0.0.0.0:8220->8220/tcp, :::8220->8220/tcp fleet-server
affda2fbda93 docker.elastic.co/kibana/kibana:8.8.2 "/bin/tini -- /usr/l…" 14 months ago Up 4 minutes (unhealthy) 0.0.0.0:5601->5601/tcp, :::5601->5601/tcp kibana
06c71b5eee30 docker.elastic.co/elasticsearch/elasticsearch:8.8.2 "/bin/tini -- /usr/l…" 14 months ago Up 13 minutes (healthy) 0.0.0.0:9200->9200/tcp, :::9200->9200/tcp, 9300/tcp elasticsearch
11508d6a20ea docker.elastic.co/elasticsearch/elasticsearch:8.8.2 "/bin/tini -- /usr/l…" 14 months ago Exited (0) 14 months ago
And a curl to localhost:9200 gets a connection refused:
elastic@ip-172-31-8-179:~/elastic-agent-8.8.2-linux-x86_64$ docker exec kibana curl -XGET 127.0.0.1:9200
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to 127.0.0.1 port 9200: Connection refused
Are there any other troubleshooting steps I can take here, or can the lab be reset to its original state?
Thanks