# Kibana waiting for elasticsearch

**URL:** <https://discuss.elastic.co/t/kibana-waiting-for-elasticsearch/160539>\
**Category:** Kibana\
**Created:** [December 12, 2018, 12:20pm UTC](https://discuss.elastic.co/t/kibana-waiting-for-elasticsearch/160539 "2018-12-12T12:20:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nyuncampy](https://avatars.discourse-cdn.com/v4/letter/n/ecd19e/32.png) [@Nyuncampy](https://discuss.elastic.co/u/Nyuncampy)\
**Post date:** [December 12, 2018, 12:20pm UTC](https://discuss.elastic.co/t/kibana-waiting-for-elasticsearch/160539/1 "2018-12-12T12:20:20Z")

</div>

Hi! I'm using docker-compose to create an ELK stack. When I start the stack and look at the Kibana logs I can see that it just gets stuck waiting for elasticsearch.

Log output:

[root@fdesmonitor02 stack-elk]# docker-compose logs -f kibana  
kibana\_1 | {"type":"log","@timestamp":"2018-12-12T12:06:58Z","tags":["status","plugin:beats\_management@6.5.1","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}  
kibana\_1 | {"type":"log","@timestamp":"2018-12-12T12:06:58Z","tags":["status","plugin:reporting@6.5.1","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}  
kibana\_1 | {"type":"log","@timestamp":"2018-12-12T12:06:58Z","tags":["info","monitoring-ui","kibana-monitoring"],"pid":1,"message":"Starting monitoring stats collection"}  
kibana\_1 | {"type":"log","@timestamp":"2018-12-12T12:06:58Z","tags":["status","plugin:security@6.5.1","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}  
kibana\_1 | {"type":"log","@timestamp":"2018-12-12T12:06:59Z","tags":["license","info","xpack"],"pid":1,"message":"Imported license information from Elasticsearch for the [monitoring] cluster: mode: basic | status: active"}  
kibana\_1 | {"type":"log","@timestamp":"2018-12-12T12:07:01Z","tags":["reporting","warning"],"pid":1,"message":"Enabling the Chromium sandbox provides an additional layer of protection."}  
kibana\_1 | {"type":"log","@timestamp":"2018-12-12T12:07:01Z","tags":["listening","info"],"pid":1,"message":"Server running at [http://0:5601](http://0:5601)"}  
kibana\_1 | {"type":"log","@timestamp":"2018-12-12T12:07:01Z","tags":["status","plugin:spaces@6.5.1","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}

My docker-compose.yml contains this config

[root@fdesmonitor02 stack-elk]# cat docker-compose.yml  
version: '3.6'  
services:  
elasticsearch:  
image: elasticsearch:6.5.1  
restart: always  
user: "elasticsearch:elasticsearch"  
environment:  
- cluster.name=docker-cluster  
- bootstrap.memory\_lock=true  
- "ES\_JAVA\_OPTS=-Xms512m -Xmx512m"  
ulimits:  
memlock:  
soft: -1  
hard: -1  
ports:  
- "9200:9200"  
- "9300:9300"  
volumes:  
- /usr/share/zoneinfo/Europe/Madrid:/etc/localtime:ro  
- ./storage/elasticsearch/data:/usr/share/elasticsearch/data  
- ./storage/elasticsearch/config:/usr/share/elasticsearch/config  
- ./storage/elasticsearch/logs:/usr/share/elasticsearch/logs  
- ./storage/elasticsearch/plugins:/usr/share/elasticsearch/plugins

```
networks:
  - internal

```

kibana:  
image: kibana:6.5.1  
restart: always  
expose:  
- 5601  
volumes:  
- /usr/share/zoneinfo/Europe/Madrid:/etc/localtime:ro  
- ./storage/kibana/conf:/etc/kibana/  
- ./storage/kibana/data:/var/lib/kibana/  
environment:  
- "ELASTICSEARCH\_URL=http://elasticsearch:9200"  
- "xpack.security.enabled=false"  
labels:  
- traefik.enable=true  
- traefik.docker.network=traefiknet  
- traefik.frontend.entryPoints=http,https  
- traefik.internal.backend=Internal  
- traefik.internal.domain=internal.lan  
- "traefik.internal.frontend.rule=Host:fdesmonitor02.internal.lan,PathPrefixStrip:/kibana"  
- traefik.internal.port=5601  
networks:  
- internal  
- traefiknet

logstash:  
image: logstash:6.5.1  
restart: always  
ports:  
- "5000:5000"  
volumes:  
- /usr/share/zoneinfo/Europe/Madrid:/etc/localtime:ro  
- ./storage/logstash/conf:/etc/logstash/  
- ./storage/logstash/data:/var/lib/logstash/  
- ./storage/logstash/logs:/var/log/logstash/  
networks:  
- internal

networks:  
traefiknet:  
external: true  
internal:  
external: false

When I try to access Kibana from firefox y get the following code.

{"statusCode":404,"error":"Not Found","message":"Not Found"}

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [December 12, 2018, 9:52pm UTC](https://discuss.elastic.co/t/kibana-waiting-for-elasticsearch/160539/2 "2018-12-12T21:52:15Z")

</div>

cc'ng my colleague @jarpy for more insights into this.

Thanks  
Rashmi

---

<div class="post-metadata">

**Author:** ![jarpy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jarpy/32/51290_2.png) [@jarpy](https://discuss.elastic.co/u/jarpy)\
**Post date:** [December 13, 2018, 3:24am UTC](https://discuss.elastic.co/t/kibana-waiting-for-elasticsearch/160539/3 "2018-12-13T03:24:18Z")

</div>

Hi,

Please format your files with "triple-ticks". YAML is whitespace sensitive.

[https://help.github.com/articles/creating-and-highlighting-code-blocks/](https://help.github.com/articles/creating-and-highlighting-code-blocks/)

Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 10, 2019, 3:31am UTC](https://discuss.elastic.co/t/kibana-waiting-for-elasticsearch/160539/4 "2019-01-10T03:31:58Z")

</div>

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