Curator no longer runs properly


(Daragh) #1

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


(Aaron Mildenstein) #2

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?


(Daragh) #3

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


(system) #4

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