# Curator 5.4.1 exits gracefully but does nothing

**URL:** <https://discuss.elastic.co/t/curator-5-4-1-exits-gracefully-but-does-nothing/111071>\
**Category:** Elasticsearch\
**Created:** [December 11, 2017, 10:59am UTC](https://discuss.elastic.co/t/curator-5-4-1-exits-gracefully-but-does-nothing/111071 "2017-12-11T10:59:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jalker](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@jalker](https://discuss.elastic.co/u/jalker)\
**Post date:** [December 11, 2017, 10:59am UTC](https://discuss.elastic.co/t/curator-5-4-1-exits-gracefully-but-does-nothing/111071/1 "2017-12-11T10:59:11Z")

</div>

I have just installed curator 5.4.1 on a CentOS 7 machine to access an Elasticsearch 5.6 instance.  
The install seems okay

$curator --version  
curator, version 5.4.1

but curator always exits gracefully with an exit status 0 without doing anything. Same thing for curator\_cli.

The behavior is always the same even if I only put garbage the configuration file.

$curator action.yml  
$echo $?  
0

Any insight will be appreciated.

---

<div class="post-metadata">

**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:** [December 11, 2017, 11:30am UTC](https://discuss.elastic.co/t/curator-5-4-1-exits-gracefully-but-does-nothing/111071/2 "2017-12-11T11:30:01Z")

</div>

Curious. I tested the package on a CentOS 7 machine, and it works for me:

```auto
[buh@centos7-pkg-test curator_packages]$ cat /etc/redhat-release
CentOS Linux release 7.2.1511 (Core)
[buh@centos7-pkg-test curator_packages]$ curator --version
curator, version 5.4.1
[buh@centos7-pkg-test curator_packages]$ curator --dry-run --config curator.yml open-test.yml
2017-12-11 11:28:58,105 INFO Preparing Action ID: 1, "open"
2017-12-11 11:28:58,109 INFO Trying Action ID: 1, "open": open all indices older than 1 day should only use with --dry-run as test for output
2017-12-11 11:28:58,394 INFO DRY-RUN MODE. No changes will be made.
2017-12-11 11:28:58,394 INFO (CLOSED) indices may be shown that may not be acted on by action "open".
2017-12-11 11:28:58,394 INFO DRY-RUN: open: .kibana with arguments: {}
2017-12-11 11:28:58,394 INFO DRY-RUN: open: .ml-anomalies-shared with arguments: {}
2017-12-11 11:28:58,394 INFO DRY-RUN: open: .ml-notifications with arguments: {}
... Lots more indices here ...
2017-12-11 11:28:58,397 INFO Action ID: 1, "open" completed.
2017-12-11 11:28:58,397 INFO Job completed.

```

---

<div class="post-metadata">

**Author:** ![jalker](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@jalker](https://discuss.elastic.co/u/jalker)\
**Post date:** [December 11, 2017, 11:48am UTC](https://discuss.elastic.co/t/curator-5-4-1-exits-gracefully-but-does-nothing/111071/3 "2017-12-11T11:48:11Z")

</div>

Thanks for your help.

```auto
[admin_kering@kgxch1delk01 ~]$ cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)
[admin_kering@kgxch1delk01 ~]$ curator --dry-run actions.yml
[admin_kering@kgxch1delk01 ~]$ echo $?
0
[admin_kering@kgxch1delk01 ~]$

```

Is there some kind of "magic" debug option I could use to try to understand what's going on?

---

<div class="post-metadata">

**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:** [December 11, 2017, 12:17pm UTC](https://discuss.elastic.co/t/curator-5-4-1-exits-gracefully-but-does-nothing/111071/4 "2017-12-11T12:17:03Z")

</div>

What's in your `~/.curator/curator.yml` file?

---

<div class="post-metadata">

**Author:** ![jalker](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@jalker](https://discuss.elastic.co/u/jalker)\
**Post date:** [December 11, 2017, 1:01pm UTC](https://discuss.elastic.co/t/curator-5-4-1-exits-gracefully-but-does-nothing/111071/5 "2017-12-11T13:01:37Z")

</div>

Eye-opener 🙂 Trying to cut and paste curator.yml onto this board, I've realized there was a spurious non ASCII character at the beginning of the 1st line.  
No clue why but the problem is solved anyway.  
Thanks again.

---

<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:** [January 8, 2018, 1:01pm UTC](https://discuss.elastic.co/t/curator-5-4-1-exits-gracefully-but-does-nothing/111071/6 "2018-01-08T13:01:37Z")

</div>

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