# Curator no longer runs properly

**URL:** <https://discuss.elastic.co/t/curator-no-longer-runs-properly/73090>\
**Category:** Elasticsearch\
**Created:** [January 28, 2017, 4:40pm UTC](https://discuss.elastic.co/t/curator-no-longer-runs-properly/73090 "2017-01-28T16:40:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmcn\_es](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@dmcn\_es](https://discuss.elastic.co/u/dmcn_es)\
**Post date:** [January 28, 2017, 4:40pm UTC](https://discuss.elastic.co/t/curator-no-longer-runs-properly/73090/1 "2017-01-28T16:40:52Z")

</div>

hi  
would appreciate help with this issue.  
I suspect the issue lies in elasticsearch but can not find it.

Issue :-  
Although curator dry-run did run sucessfully in the recent past (this week), now it does not run due to below error :-

[root@logstash1 elasticsearch-curator]# curator --dry-run --config /opt/elasticsearch-curator/curator.yaml

delete\_indices.yaml  
2017-01-27 12:07:26,393 INFO Preparing Action ID: 1, "delete\_indices"  
Unable to create client connection to Elasticsearch. Error: ConnectionError(\<urllib3.connection.HTTPConnection object at

0x7f1d239cd588\>: Failed to establish a new connection: [Errno 111] Connection refused) caused by: NewConnectionError

(\<urllib3.connection.HTTPConnection object at 0x7f1d239cd588\>: Failed to establish a new connection: [Errno 111] Connection

refused)

Thanks,  
Daragh

---

<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:** [January 28, 2017, 5:16pm UTC](https://discuss.elastic.co/t/curator-no-longer-runs-properly/73090/2 "2017-01-28T17:16:38Z")

</div>

A failure to connect message (refused, even) suggests that the client node is unreachable. Have you checked whether curl or other checks work against the host and port configured in your curator.yml file?

---

<div class="post-metadata">

**Author:** ![dmcn\_es](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@dmcn\_es](https://discuss.elastic.co/u/dmcn_es)\
**Post date:** [January 30, 2017, 12:08pm UTC](https://discuss.elastic.co/t/curator-no-longer-runs-properly/73090/3 "2017-01-30T12:08:58Z")

</div>

hi Aaron,  
when I fixed to other error I logged with subject :-

"Curl test command does"

Now curator also runs properly and I can run the dry-run as a test successfully.

Thanks,  
Daragh

---

<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:** [February 27, 2017, 12:09pm UTC](https://discuss.elastic.co/t/curator-no-longer-runs-properly/73090/4 "2017-02-27T12:09:00Z")

</div>

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