S
S
Sergey_mur2018-04-03 22:03:13
Debian
Sergey_mur, 2018-04-03 22:03:13

What could be the problem with Elasticsearch curator?

I have ELK cluster version 6.2.2.
To remove old indexes, I'm trying to set up Curator version 5.5.1, which is the latest at the moment.
Also, Search Guard is rolled on ELK as the latest version.
Essence of the question: when running ./curator_cli --host logstash.taxnet.ru --port 9200 --http_auth admin:admin --loglevel DEBUG --logfile '/var/log/curator/curator.log' show_indices --filter_list' {"filtertype":"pattern","kind":"prefix","value":"test"}' I get the desired response as a list of matching indexes. I also get extensive information in the specified log file. When I try to run ./curator --config ~/.curator/curator.yml ~/.curator/action_file.yml I get nothing. Even messages to the console. The log file is also silent. Before that, changes in the configuration file were not read, that is, the logs somehow went and, judging by them, any configuration changes were ignored.
curator.yml file content:

client:
  hosts:
    - logstash.taxnet.ru
  port: 9200
  url_prefix:
  use_ssl: True
  certificate: root-ca.pem
  client_cert: 
  client_key: 
  ssl_no_validate: True
  http_auth: admin:admin
  timeout: 30
  master_only: False
logging:
  loglevel: INFO
  logfile: #'/var/log/curator/curator.log'
  logformat: default
  blacklist: []

Content of action_file.yml:
actions:
  1:
    action: 'open'
    description: show test action
    options:
      continue_if_exception: True
      disable_action: False
    filters:
    - filtertype: pattern
       kind: prefix
       value: test

Answer the question

In order to leave comments, you need to log in

1 answer(s)
S
Sergey_mur, 2018-04-03
@Sergey_mur

everything was solved by installing via pip.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question