# Curator not running

**URL:** <https://discuss.elastic.co/t/curator-not-running/143338>\
**Category:** Elasticsearch\
**Created:** [August 7, 2018, 1:29pm UTC](https://discuss.elastic.co/t/curator-not-running/143338 "2018-08-07T13:29:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndyT](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@AndyT](https://discuss.elastic.co/u/AndyT)\
**Post date:** [August 7, 2018, 1:29pm UTC](https://discuss.elastic.co/t/curator-not-running/143338/1 "2018-08-07T13:29:24Z")

</div>

Hi,

Trying to setup some curator jobs to delete data that's over a year old. Have curator installed via YUM.

Have the following in my curator.yml

```
client:
  hosts:
    - 127.0.0.1
  port: 9200
  url_prefix:
  use_ssl: True
  certificate: '/etc/elasticsearch/x-pack/ca.crt'
  client_cert: '/etc/elasticsearch/x-pack/master1/master1.crt'
  client_key: '/etc/elasticsearch/x-pack/master1/master1.key'
  ssl_no_validate: False
  http_auth:
  timeout: 30
  master_only: False

logging:
  loglevel: DEBUG
  logfile: '/var/logs/curator.log'
  logformat: default
  blacklist: ['elasticsearch', 'urllib3']

```

And the following in my actions file.

```
actions:
  1:
    action: delete_indices
    description: delete indices that are older than 365 days
    filters:
    -
      filtertype: age
      source: creation_date
      direction: older
      unit: days
      unit_count: 365
    -
      filtertype: kibana
      exclude: True

```

If I run "curator --dry-run --config ~/.curator/curator.yml delete-old-indices.yml" then I get no output on the command line and only the following in the debug log.

```
2018-08-07 14:25:20,521 INFO curator.cli run:146 Preparing Action ID: 1, "delete_indices"
2018-08-07 14:25:20,521 DEBUG curator.utils get_client:803 kwargs = {'hosts': ['127.0.0.1'], 'port': 9200, 'use_ssl': True, 'certificate': '/etc/elasticsearch/x-pack/ca.crt', 'client_cert': '/etc/elasticsearch/x-pack/master1/master1.crt', 'client_key': '/etc/elasticsearch/x-pack/master1/master1.key', 'ssl_no_validate': False, 'master_only': False, 'aws_secret_key': None, 'aws_sign_request': False, 'url_prefix': '', 'aws_token': None, 'http_auth': None, 'aws_key': None, 'timeout': 30}
2018-08-07 14:25:20,521 DEBUG curator.utils get_client:809 Attempting to verify SSL certificate.
2018-08-07 14:25:20,530 DEBUG curator.utils get_client:880 Not using "requests_aws4auth" python module to connect.

```

Looks as if it attempts to verify the certs but then doesn't do anything else. No errors output in the log or stdout.

---

<div class="post-metadata">

**Author:** ![AndyT](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@AndyT](https://discuss.elastic.co/u/AndyT)\
**Post date:** [August 7, 2018, 1:33pm UTC](https://discuss.elastic.co/t/curator-not-running/143338/2 "2018-08-07T13:33:20Z")

</div>

Full debug log is here - [https://pastebin.com/HFEqygS4](https://pastebin.com/HFEqygS4)

---

<div class="post-metadata">

**Author:** ![AndyT](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@AndyT](https://discuss.elastic.co/u/AndyT)\
**Post date:** [August 7, 2018, 2:28pm UTC](https://discuss.elastic.co/t/curator-not-running/143338/3 "2018-08-07T14:28:39Z")

</div>

Removing the client cert and key and specifying a http\_auth user/pass seemed to work instead.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 4, 2018, 2:28pm UTC](https://discuss.elastic.co/t/curator-not-running/143338/4 "2018-09-04T14:28:53Z")

</div>

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