# Curator running problem

**URL:** <https://discuss.elastic.co/t/curator-running-problem/89257>\
**Category:** Elasticsearch\
**Created:** [June 13, 2017, 7:28pm UTC](https://discuss.elastic.co/t/curator-running-problem/89257 "2017-06-13T19:28:50Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ximeng\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ximeng_zhao/32/15775_2.png) [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)\
**Post date:** [June 13, 2017, 7:28pm UTC](https://discuss.elastic.co/t/curator-running-problem/89257/1 "2017-06-13T19:28:50Z")

</div>

Hi all,

I have installed curator via RPM package on CentOS 6.7. I tried to delete some indices on elastic search.  
But when I tried to run curator, it gives error as below.

2017-06-13 15:13:21,660 DEBUG curator.cli cli: 135 action\_disabled = False  
2017-06-13 15:13:21,660 DEBUG curator.cli cli: 139 continue\_if\_exception = False  
2017-06-13 15:13:21,660 DEBUG curator.cli cli: 141 timeout\_override = None  
2017-06-13 15:13:21,660 DEBUG curator.cli cli: 143 ignore\_empty\_list = False  
2017-06-13 15:13:21,660 INFO curator.cli cli: 153 Preparing Action ID: 1, "delete\_indices"  
2017-06-13 15:13:21,660 DEBUG curator.utils get\_client: 714 kwargs = {'hosts': ['127.31.21.47:9200'], 'use\_ssl': False, 'ssl\_no\_validat e': False, 'master\_only': False, 'client\_key': None, 'aws\_secret\_key': None, 'ce rtificate': None, 'aws\_region': None, 'http\_auth': None, 'client\_cert': None, 'u rl\_prefix': '', 'aws\_key': None, 'port': 9200, 'timeout': 30}  
2017-06-13 15:13:21,664 DEBUG curator.utils get\_client: 764 Not using "requests\_aws4auth" python module to connect.  
Unable to create client connection to Elasticsearch. Error: ConnectionError(\<ur llib3.connection.HTTPConnection object at 0x7f4ea09b7c50\>: Failed to establish a new connection: [Errno 111] Connection refused) caused by: NewConnectionError(\< urllib3.connection.HTTPConnection object at 0x7f4ea09b7c50\>: Failed to establish a new connection: [Errno 111] Connection refused)

Please let me know if you have any ideas, thanks so much.

Elasticsearch version is 5.2.2  
Curator version is 5.1.1.

---

<div class="post-metadata">

**Author:** ![Ximeng\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ximeng_zhao/32/15775_2.png) [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)\
**Post date:** [June 13, 2017, 7:35pm UTC](https://discuss.elastic.co/t/curator-running-problem/89257/2 "2017-06-13T19:35:33Z")

</div>

Just want to add something that I just found here. I did not have python installed, which python version I need to choose.

---

<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:** [June 13, 2017, 8:01pm UTC](https://discuss.elastic.co/t/curator-running-problem/89257/3 "2017-06-13T20:01:40Z")

</div>

> [@Ximeng\_Zhao](#):
>
> I did not have python installed, which python version I need to choose.

Since you installed via the RPM, Python is bundled with that. You don't need a separate Python.

> [@Ximeng\_Zhao](#):
>
> Failed to establish a new connection: [Errno 111] Connection refused)

This indicates that the host you specified, `127.31.21.47:9200`, is not reachable by Curator, or Elasticsearch is not running on port 9200 at that IP address..

---

<div class="post-metadata">

**Author:** ![Ximeng\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ximeng_zhao/32/15775_2.png) [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)\
**Post date:** [June 13, 2017, 8:21pm UTC](https://discuss.elastic.co/t/curator-running-problem/89257/4 "2017-06-13T20:21:47Z")

</div>

@theuntergeek

Thanks for your reply. I have checked Elasticsearch via typing curl "127.31.21.47:9200" from the terminal, it runs well.  
I also checked the config.yml, like this:  
client:  
hosts: ["127.31.21.47:9200"]

Why it cannot reachable? Thanks.

---

<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:** [June 13, 2017, 8:38pm UTC](https://discuss.elastic.co/t/curator-running-problem/89257/5 "2017-06-13T20:38:06Z")

</div>

By changing the `logging:` block in your `config.yml` file to have `blacklist: []`, and `loglevel: DEBUG`, you will receive more debug information. I can't answer why `curl` works, and `Curator` can't. The error `Unable to create client connection to Elasticsearch.` is pretty clear, though.

Please run with these settings changed, and include the last 20 or so lines of the log after attempting again.

---

<div class="post-metadata">

**Author:** ![Ximeng\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ximeng_zhao/32/15775_2.png) [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)\
**Post date:** [June 13, 2017, 9:03pm UTC](https://discuss.elastic.co/t/curator-running-problem/89257/6 "2017-06-13T21:03:11Z")

</div>

@theuntergeek

Here's the information that I got after the change based on your suggestion.  
2017-06-13 16:58:48,620 DEBUG elasticsearch log\_request\_fail:105 \> None  
2017-06-13 16:58:48,620 DEBUG urllib3.util.retry from\_int:200 Converted retries value: False -\> Retry(t otal=False, connect=None, read=None, redirect=0, status=None)  
2017-06-13 16:58:48,620 DEBUG urllib3.connectionpool \_new\_conn:207 Starting new HTTP connection (4): 127.31. 21.47  
2017-06-13 16:58:48,620 WARNING elasticsearch log\_request\_fail:97 GET [http://127.31.21.47:9200/](http://127.31.21.47:9200/) [status:N/A request:0.000s]  
Traceback (most recent call last):  
File "/home/buh/.local/lib/python3.6/site-packages/urllib3/connection.py", line 141, in \_new\_conn  
File "/home/buh/.local/lib/python3.6/site-packages/urllib3/util/connection.py", line 83, in create\_connection  
File "/home/buh/.local/lib/python3.6/site-packages/urllib3/util/connection.py", line 73, in create\_connection  
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):  
File "/home/buh/.local/lib/python3.6/site-packages/elasticsearch/connection/http\_urllib3.py", line 114, in perform\_request  
File "/home/buh/.local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 649, in urlopen  
File "/home/buh/.local/lib/python3.6/site-packages/urllib3/util/retry.py", line 333, in increment  
File "/home/buh/.local/lib/python3.6/site-packages/urllib3/packages/six.py", line 686, in reraise  
File "/home/buh/.local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 600, in urlopen  
File "/home/buh/.local/lib/python3.6/site-packages/urllib3/connectionpool.py", line 356, in \_make\_request  
File "/usr/local/lib/python3.6/http/client.py", line 1239, in request  
File "/usr/local/lib/python3.6/http/client.py", line 1285, in \_send\_request  
File "/usr/local/lib/python3.6/http/client.py", line 1234, in endheaders  
File "/usr/local/lib/python3.6/http/client.py", line 1026, in \_send\_output  
File "/usr/local/lib/python3.6/http/client.py", line 964, in send  
File "/home/buh/.local/lib/python3.6/site-packages/urllib3/connection.py", line 166, in connect  
File "/home/buh/.local/lib/python3.6/site-packages/urllib3/connection.py", line 150, in \_new\_conn  
urllib3.exceptions.NewConnectionError: \<urllib3.connection.HTTPConnection object at 0x7f8a9e572ef0\>: Failed to establish a new connection: [Errno 111] Connection refused  
2017-06-13 16:58:48,621 DEBUG elasticsearch log\_request\_fail:105 \> None  
Unable to create client connection to Elasticsearch. Error: ConnectionError(\<urllib3.connection.HTTPConnection object at 0x7f 8a9e572ef0\>: Failed to establish a new connection: [Errno 111] Connection refused) caused by: NewConnectionError(\<urllib3.conn ection.HTTPConnection object at 0x7f8a9e572ef0\>: Failed to establish a new connection: [Errno 111] Connection refused)

---

<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:** [June 13, 2017, 9:49pm UTC](https://discuss.elastic.co/t/curator-running-problem/89257/7 "2017-06-13T21:49:47Z")

</div>

It's quite clear that Curator cannot form a connection, regardless of what `curl` may reveal. On that subject, what do you see when you run `curl http://127.31.21.47:9200/`?

---

<div class="post-metadata">

**Author:** ![Ximeng\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ximeng_zhao/32/15775_2.png) [@Ximeng\_Zhao](https://discuss.elastic.co/u/Ximeng_Zhao)\
**Post date:** [June 13, 2017, 9:56pm UTC](https://discuss.elastic.co/t/curator-running-problem/89257/8 "2017-06-13T21:56:44Z")

</div>

@theuntergeek

I found the stupid mistake... I put 127 instead of 172... , now it's working. thanks so much.  
By the way, can you take a look at this question about elasticsearch? Here's the link.

> [@Restart elasticsearch issue](https://discuss.elastic.co/t/restart-elasticsearch-issue/89266):
>
> Hi all, When I restart to run elasticsearch \<version=5.2.2\>, it gives me some error here. [2017-06-13T16:09:30,700][INFO][o.e.n.Node] [] initializing ... [2017-06-13T16:09:30,790][WARN][o.e.b.ElasticsearchUncaughtExceptionHandler] [] uncaught exception in thread [main] org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: failed to obtain node locks, tried [[/datab/mastertest]] with lock id [0]; maybe these locations are not writable or multiple node…

---

<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:** [July 11, 2017, 9:57pm UTC](https://discuss.elastic.co/t/curator-running-problem/89257/9 "2017-07-11T21:57:27Z")

</div>

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