Curator is running but not deleting any index in elastic search and not printing any logs

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
ports:
- '9200:9200'
environment:
- discovery.type=single-node
ulimits:
memlock:
soft: -1
hard: -1

logstash:
image: 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" ]
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

I recommend changing this:

to this:

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.

even after changing this facing same issue.
This is my curator.yml file:-
client:
hosts: [ "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?

With docker, I'm thinking that logfile: should be empty, so that it logs to STDOUT. From the Curator documentation:

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.

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