# Curator - Unable to run any commands
**URL:** https://discuss.elastic.co/t/curator-unable-to-run-any-commands/109512
**Category:** Elasticsearch
**Created:** [November 29, 2017, 6:02am UTC](https://discuss.elastic.co/t/curator-unable-to-run-any-commands/109512 "2017-11-29T06:02:42Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Sjaak01](https://discuss.elastic.co/u/Sjaak01)
#### Post date: [November 29, 2017, 6:02am UTC](https://discuss.elastic.co/t/curator-unable-to-run-any-commands/109512/1 "2017-11-29T06:02:43Z")
Hi,
I just installed curator but I'm unable to run anything.
Curator ACTION\_FILE.YML results in error no such command.
Other things I don't understand are:
1. Version is listed as 5.4.0 but running --version I always get 3.4.1. I even tried the pip command with the specified version.
2. No configuration file was present in home/user/.curator. Actually I didn't even have that folder after installation.
3. I tried creating the folder and the config file manually (copy/pasted the config file from the docs) but that isn't working.
---
### Author:  [@Sjaak01](https://discuss.elastic.co/u/Sjaak01)
#### Post date: [November 29, 2017, 6:34am UTC](https://discuss.elastic.co/t/curator-unable-to-run-any-commands/109512/2 "2017-11-29T06:34:17Z")
Tried installing on a different system and the same issue.
.deb shows 5.4.0 as version but after installation it jumps to 3.4.1.1. Also no .curator folder created in the home folder. Locate doesn't find any folders or files named curator either.
---
### Author:  [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [November 29, 2017, 2:43pm UTC](https://discuss.elastic.co/t/curator-unable-to-run-any-commands/109512/3 "2017-11-29T14:43:17Z")
1. I think you'll find that if you uninstall it, that it's still installed as 3.4.1. You have multiple versions installed, and the system is finding 3.4.1 instead. Version 3.4.1 is in some of the core repositories out there.
2. Curator does not automatically create a config file or config directory. You have to create those yourself.
3. If the system finds 3.4.1 first in the system path, instead of 5.4.0, this is a likely outcome.
---
### Author:  [@Sjaak01](https://discuss.elastic.co/u/Sjaak01)
#### Post date: [December 1, 2017, 7:18am UTC](https://discuss.elastic.co/t/curator-unable-to-run-any-commands/109512/4 "2017-12-01T07:18:38Z")
Thanks.
I don't know why but for some reason the next morning the version did show up as 5.4.0. After creating the config and action files I had no problems running curator.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 29, 2017, 7:18am UTC](https://discuss.elastic.co/t/curator-unable-to-run-any-commands/109512/5 "2017-12-29T07:18:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.