Kibana waiting for elasticsearch

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"}
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"}

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

Thanks
Rashmi

Hi,

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

https://help.github.com/articles/creating-and-highlighting-code-blocks/

Thanks.

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