Connectivity Issue with Curator taking on ElasticCloud in Windows 10


We have the elk setup on Elastic Cloud and I have a requirement to delete the indices from a curator.
The following code is the curator config:
hosts: [ "" ]
port: 9254
use_ssl: True
http_auth: elastic:elastic
timeout: 1000
master_only: False

loglevel: INFO
logfile: C:\logs.log
logformat: default
blacklist: ['elasticsearch', 'urllib3']

The following code is the action file:
action: delete_indices
description: >-
Delete indices older than 30 days (based on index name), for navis-apex-ec2amaz-ul066bg-2019.10.*
prefixed indices. Ignore the error if the filter does not result in an
actionable list of indices (ignore_empty_list) and exit cleanly.
ignore_empty_list: True
continue_if_exception: False
disable_action: False
- filtertype: pattern
kind: prefix
value: ul066bg-2019.10.*
- filtertype: age
source: name
direction: older
timestring: '%Y.%m.%d'
unit: days
unit_count: 30

The same action file, works fine with a local cluster(localhost) but not with the ElasticCloud service.

The following was the response after running the curator:
2020-03-06 02:18:41,723 INFO Preparing Action ID: 1, "delete_indices"
2020-03-06 02:18:41,723 INFO Creating client object and testing connection
2020-03-06 02:18:41,726 INFO Instantiating client object
2020-03-06 02:18:41,726 INFO Testing client connectivity
2020-03-06 02:24:18,077 ERROR HTTP N/A error: HTTPSConnectionPool(host='', port=9254): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x00000197C498D160>: Failed to establish a new connection: [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'))
2020-03-06 02:24:18,077 CRITICAL Curator cannot proceed. Exiting.

Note: The host is modified for security reason.

Please assist.

Thanks, Brit

Moved this to elasticsearch as I think it's a more general "how to use a client" question, but it looks like the port you've specified is wrong - it should be either 443 or equivalently 9243

1 Like

Thanks Alex. You made my day.
I couldn't believe I made a typo on port.

The port was supposed to be 9243 instead of 9254.

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