Kibana_task_manager docs getting deleted. Kibana not starting

[akshatBais (Akshat Singh Bais)]

I am getting this error while running , elasticsearch , logstash and kibana via docker compose :

{"type":"error","@timestamp":"2019-10-17T12:48:31Z","tags":["warning","stats-collection"],"pid":1,"level":"error","error":{"message":"[index_not_found_exception] no such index [.kibana], with { resource.type="index_or_alias" & resource.id=".kibana" & index_uuid="na" & index=".kibana" }",

Also I see

green open .kibana_task_manager JFExqGGOQgq7sDd8chX_NQ 1 0 2 8 108.9kb 108.9kb

where deleted_docs is increasing.

Below is my docker-compose file :

version: "3.2"
services:
elasticsearch:
image: docker.elastic.co/elasticsearch/elasticsearch:7.2.0
container_name: elasticsearch
environment:
- node.name=es01
- cluster.name=v18-es-cluster
- cluster.initial_master_nodes=es01
ports:
- 9200:9200
- 9300:9300
volumes:
- esdata:/usr/share/elasticsearch/data
networks:
- stack
logstash:
image: logstash:0.0.2
container_name: logstash
ports:
- 9600:9600
volumes:
- api_logs:/usr/tmp/
networks:
- stack
depends_on:
- elasticsearch
kibana:
image: docker.elastic.co/kibana/kibana:7.2.0
container_name: kibana
ports:
- 5601:5601
networks:
- stack
depends_on:
- elasticsearch
environment:
- ELASTICSEARCH_URL= http://172.25.16.132:9200
volumes:
esdata:
api_logs:
external: true
networks:
stack:

I am getting data from logstash to elasticsearch , just that kibana is not working and I get this message "Kibana server is not ready yet" on kibana url.

What am I doing wrong while configuring docker compose, or what steps shall I take to make kibana running using docker-compose

[lukas (Lukas Olson)]

@tylersmalley @jbudz Any input here?

[tylersmalley]

@mikecote would be better to know what's going on here. Thoughts?

[mikecote (Mike)]

@tylersmalley I think the docs getting deleted is normal for task manager. Elasticsearch considers an update a delete+insert so each time the task manager updates a task, it will cause the deleted_docs count to increase.

From what I can see, there's 2 existing tasks which is the normal number of tasks that get registered on a fresh Kibana setup.

It seems setup is stuck on something else than task manager by looking at the stats-collection error.