# Where to get curator\_cli?

**URL:** <https://discuss.elastic.co/t/where-to-get-curator-cli/96687>\
**Category:** Elasticsearch\
**Created:** [August 11, 2017, 12:23am UTC](https://discuss.elastic.co/t/where-to-get-curator-cli/96687 "2017-08-11T00:23:24Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![marksarnold](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marksarnold/32/25611_2.png) [@marksarnold](https://discuss.elastic.co/u/marksarnold)\
**Post date:** [August 11, 2017, 12:23am UTC](https://discuss.elastic.co/t/where-to-get-curator-cli/96687/1 "2017-08-11T00:23:24Z")

</div>

Hello,  
I installed curator from the APT repo as per [https://www.elastic.co/guide/en/elasticsearch/client/curator/current/apt-repository.html](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/apt-repository.html)  
After the installation, I have the curator binary in /usr/bin, but there is no curator\_cli.  
dpkg-query -L shows that there is no curator\_cli in the package.  
There also doesnt seem to be a separate curator\_cli package in the repo.

Where do I get it from?

Thank you!

---

<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:** [August 11, 2017, 6:53am UTC](https://discuss.elastic.co/t/where-to-get-curator-cli/96687/2 "2017-08-11T06:53:36Z")

</div>

`/usr/bin/curator` should be a symlink to `/opt/elasticsearch-curator/curator`, and the `curator_cli` should also reside there.

---

<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:** [August 11, 2017, 3:09pm UTC](https://discuss.elastic.co/t/where-to-get-curator-cli/96687/3 "2017-08-11T15:09:24Z")

</div>

I just installed the latest (5.1.2) into a VM to ensure I wasn't imagining it:

```auto
buh@ubuntu1604-pkg-test:~$ curator --version
curator, version 5.1.2
buh@ubuntu1604-pkg-test:~$ ls -l /usr/bin | grep curator
lrwxrwxrwx 1 root root 34 Aug 8 21:27 curator -> /opt/elasticsearch-curator/curator
lrwxrwxrwx 1 root root 38 Aug 8 21:27 curator_cli -> /opt/elasticsearch-curator/curator_cli
lrwxrwxrwx 1 root root 38 Aug 8 21:27 es_repo_mgr -> /opt/elasticsearch-curator/es_repo_mgr

```

---

<div class="post-metadata">

**Author:** ![marksarnold](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marksarnold/32/25611_2.png) [@marksarnold](https://discuss.elastic.co/u/marksarnold)\
**Post date:** [August 11, 2017, 6:24pm UTC](https://discuss.elastic.co/t/where-to-get-curator-cli/96687/4 "2017-08-11T18:24:59Z")

</div>

After I had researched all the points below, I noticed that although I followed the 5.1 install instructions, I ended up with curator version 3.4.1. Maybe that's the root cause.  
If not , here are the other things I checked:

Mine is completely different. /usr/bin/curator is not a link. It is a python script:

```
$ ls -l /usr/bin/curator
-rwxr-xr-x 1 root root 343 Feb 13 2016 /usr/bin/curator

$ cat /usr/bin/curator
#!/usr/bin/python
# EASY-INSTALL-ENTRY-SCRIPT: 'elasticsearch-curator==3.4.1','console_scripts','curator'
__requires__ = 'elasticsearch-curator==3.4.1'
import sys
from pkg_resources import load_entry_point

if __name__ == ' __main__':
    sys.exit(
        load_entry_point('elasticsearch-curator==3.4.1', 'console_scripts', 'curator')()
    )

```

Did you install the apt / deb package or some other package?

The package content has no ...\_cli either:

```
$ dpkg-query -L elasticsearch-curator
/.
/usr
/usr/bin
/usr/bin/es_repo_mgr
/usr/bin/curator
/usr/share
/usr/share/doc
/usr/share/doc/elasticsearch-curator
/usr/share/doc/elasticsearch-curator/copyright
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/es_repo_mgr.1.gz
/usr/share/man/man1/curator.1.gz
/usr/share/doc/elasticsearch-curator/changelog.Debian.gz
/usr/share/doc/elasticsearch-curator/NEWS.Debian.gz

```

Can you post the content of whatever /usr/bin/curator\_cli links to, and also of /usr/lib/python2.7/dist-packages/elasticsearch\_curator-3.4.1.egg-info/entry\_points.txt ?

Thank you

---

<div class="post-metadata">

**Author:** ![marksarnold](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marksarnold/32/25611_2.png) [@marksarnold](https://discuss.elastic.co/u/marksarnold)\
**Post date:** [August 11, 2017, 6:32pm UTC](https://discuss.elastic.co/t/where-to-get-curator-cli/96687/5 "2017-08-11T18:32:23Z")

</div>

The old version was in fact the problem.  
Somehow after adding the new repo in the LinuxMint software-sources manager, it had still grabbed the one from the official LinuxMint repo, which was completely outdated. Probably had not updated the package cache.

After uninstalling the old and installing the new one, curator\_cli is there...

---

<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:** [August 11, 2017, 9:15pm UTC](https://discuss.elastic.co/t/where-to-get-curator-cli/96687/6 "2017-08-11T21:15:18Z")

</div>

Sorry you had a bad experience. Several repositories out there are hosting _very_ old versions, like the 3.x tree. That started, and ended, right around the time I released RPM/DEB packages for Curator in the `packages.elastic.co` repository. Glad you got it sorted out!

---

<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 8, 2017, 9:15pm UTC](https://discuss.elastic.co/t/where-to-get-curator-cli/96687/7 "2017-09-08T21:15:34Z")

</div>

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