# Curator is running but not deleting any index in elastic search and not printing any logs **URL:** \ **Category:** Elasticsearch\ **Tags:** docker\ **Created:** [November 9, 2021, 4:55pm UTC](https://discuss.elastic.co/t/curator-is-running-but-not-deleting-any-index-in-elastic-search-and-not-printing-any-logs/288800 "2021-11-09T16:55:56Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Kumar\_Reddy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar_reddy/32/96298_2.png) [@Kumar\_Reddy](https://discuss.elastic.co/u/Kumar_Reddy)\ **Post date:** [November 9, 2021, 4:55pm UTC](https://discuss.elastic.co/t/curator-is-running-but-not-deleting-any-index-in-elastic-search-and-not-printing-any-logs/288800/1 "2021-11-09T16:55:56Z")
Hi, I am using docker-compose to run Elasticsearch with curator. Elasticsearch is working fine but curator is running but not deleting any index and not printing any logs. This is my docker-compose yml file :- version: '3.7' services: Elasticsearch: image: [docker.elastic.co/elasticsearch/elasticsearch:7.15.1](http://docker.elastic.co/elasticsearch/elasticsearch:7.15.1) ports: - '9200:9200' environment: - discovery.type=single-node ulimits: memlock: soft: -1 hard: -1 logstash: image: [docker.elastic.co/logstash/logstash:7.15.1](http://docker.elastic.co/logstash/logstash:7.15.1) ports: - '5000:5000' volumes: - type: bind source: /opt/data/magiluser/logstash/ target: /usr/share/logstash/pipeline read\_only: true - type: bind source: ./mysql/ target: /usr/share/mysql/ curator: image: anjia0532/docker-curator init: true volumes: - type: bind source: /opt/data/magiluser/curator/curator.yml target: /usr/share/curator/config/curator.yml read\_only: true - type: bind source: /opt/data/magiluser/curator/action.yml target: /usr/share/curator/config/delete\_log\_files\_curator.yml read\_only: true This is curator config file :- client: hosts: ["[mh-elkq.magilhub.com](http://mh-elkq.magilhub.com)" ] port: 9200 url\_prefix: use\_ssl: False certificate: client\_cert: client\_key: ssl\_no\_validate: False http\_auth: timeout: 30 master\_only: False logging: loglevel: INFO logfile:/opt/data/magiluser/curator/curator.log logformat: default blacklist: ['Elasticsearch'] This is my action file:- actions: 1: action: delete\_indices description: \>- Delete indices options: ignore\_empty\_list: True disable\_action: False filters: - filtertype: pattern kind: prefix value: 'tags' exclude: false - filtertype: pattern kind: prefix value: 'items' exclude: false - filtertype: age source: creation\_date direction: older unit: minutes unit\_count: 1 Please let me know how to fix this issue. And i also have another doubt how to map curator configuration files in docker-compose.yml file. And how to run corn job on curator using docker-compose.yml. Please revert me asap. Thanks, Kumar ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [November 9, 2021, 5:42pm UTC](https://discuss.elastic.co/t/curator-is-running-but-not-deleting-any-index-in-elastic-search-and-not-printing-any-logs/288800/2 "2021-11-09T17:42:15Z")
I recommend changing this: > [@Kumar\_Reddy](#): > > ```auto > logging: > loglevel: INFO > logfile:/opt/data/magiluser/curator/curator.log > logformat: default > blacklist: ['Elasticsearch'] > > ``` to this: ```auto logging: loglevel: DEBUG logfile:/opt/data/magiluser/curator/curator.log logformat: default blacklist: [] ``` In this way you will actually see the transactions between Curator and Elasticsearch, and be able to uncover why Curator appears to be running but not doing anything. Feel free to share what you uncover here for further troubleshooting. ---
**Author:** ![Kumar\_Reddy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar_reddy/32/96298_2.png) [@Kumar\_Reddy](https://discuss.elastic.co/u/Kumar_Reddy)\ **Post date:** [November 10, 2021, 12:49am UTC](https://discuss.elastic.co/t/curator-is-running-but-not-deleting-any-index-in-elastic-search-and-not-printing-any-logs/288800/3 "2021-11-10T00:49:57Z")
even after changing this facing same issue. This is my curator.yml file:- client: hosts: ["[mh-elkq.magilhub.com](http://mh-elkq.magilhub.com)" ] port: 9200 url\_prefix: use\_ssl: False certificate: client\_cert: client\_key: ssl\_no\_validate: False http\_auth: timeout: 30 master\_only: False logging: loglevel: DEBUG logfile:/opt/data/magiluser/curator/curator.log logformat: default blacklist: Can you kindly let me know the path which I specified in docker-compose.yml for curator is correct or not? ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [November 10, 2021, 4:00am UTC](https://discuss.elastic.co/t/curator-is-running-but-not-deleting-any-index-in-elastic-search-and-not-printing-any-logs/288800/4 "2021-11-10T04:00:04Z")
> [@Kumar\_Reddy](#): > > logfile:/opt/data/magiluser/curator/curator.log With docker, I'm thinking that `logfile:` should be empty, so that it logs to `STDOUT`. From the [Curator documentation](https://www.elastic.co/guide/en/elasticsearch/client/curator/5.8/configfile.html#logfile): > The default value is empty, which will result in logging to `STDOUT` , or the console. With that, you should be able to do `docker logs CONTAINERNAME` to see the output. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 8, 2021, 4:00am UTC](https://discuss.elastic.co/t/curator-is-running-but-not-deleting-any-index-in-elastic-search-and-not-printing-any-logs/288800/5 "2021-12-08T04:00:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.