Error in curator log on Date math function

Hi Team,

I am trying to take snapshot using curator and the job is successful. But i get the below error in the log file.

2018-12-11 07:39:57,048 INFO               curator.utils     parse_date_pattern:1338 "<baseut__{now{YYYY.MM.dd}}_{now{HH.mm|+02:00}}>" is using Elasticsearch date math.
2018-12-11 07:39:57,048 DEBUG              curator.utils     parse_date_pattern:1349 Fully rendered name: <ut__{now{YYYY.MM.dd}}_{now{HH.mm|+02:00}}>
2018-12-11 07:39:57,048 DEBUG              curator.utils             isdatemath:1879 opener =  <, closer = >
2018-12-11 07:39:57,048 DEBUG              curator.utils         parse_datemath:1895 Properly encapsulated, proceeding to next evaluation...
2018-12-11 07:39:57,048 DEBUG              curator.utils           get_datemath:1854 Random datemath string for extraction: <curator_get_datemath_function_qltizhfzalooqswfglbahsqtxsjoejwg-{now{YYYY.MM.dd}}_{now{HH.mm|+02:00}}>
2018-12-11 07:39:57,048 DEBUG         urllib3.util.retry               from_int:200  Converted retries value: False -> Retry(total=False, connect=None, read=None, redirect=0, status=None)
2018-12-11 07:39:57,049 DEBUG     urllib3.connectionpool          _make_request:396  https://0.0.0.0:9200 "GET /%3Ccurator_get_datemath_function_qltizhfzalooqswfglbahsqtxsjoejwg-%7Bnow%7BYYYY.MM.dd%7D%7D_%7Bnow%7BHH.mm%7C%2B02%3A00%7D%7D%3E HTTP/1.1" 404 381
2018-12-11 07:39:57,050 WARNING            elasticsearch       log_request_fail:97   GET https://0.0.0.0:9200/%3Ccurator_get_datemath_function_qltizhfzalooqswfglbahsqtxsjoejwg-%7Bnow%7BYYYY.MM.dd%7D%7D_%7Bnow%7BHH.mm%7C%2B02%3A00%7D%7D%3E [status:404 request:0.001s]
2018-12-11 07:39:57,050 DEBUG              elasticsearch       log_request_fail:105  > None
2018-12-11 07:39:57,050 DEBUG              elasticsearch       log_request_fail:110  < {"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index","index_uuid":"_na_","index":"curator_get_datemath_function_qltizhfzalooqswfglbahsqtxsjoejwg-2018.12.11_08.39"}],"type":"index_not_found_exception","reason":"no such index","index_uuid":"_na_","index":"curator_get_datemath_function_qltizhfzalooqswfglbahsqtxsjoejwg-2018.12.11_08.39"},"status":404}
2018-12-11 07:39:57,050 DEBUG              curator.utils           get_datemath:1861 Response index name for extraction: curator_get_datemath_function_qltizhfzalooqswfglbahsqtxsjoejwg-2018.12.11_08.39

Any idea why is this happening or what the curator is doing at this point?

Thanks in advance!

Hi @Elango-mas,

If you see the error its showing Request fail and index not found.

However, Request you to share the YML file for snapshot for further investigation.

Regards,
Harsh Bajaj

Hi Harsh,

snapshot.yml

actions:
  1:
    action: snapshot
    description: >-
    options:
      repository: repositoryname
      name: <snapshotname_{now{YYYY.MM.dd}}_{now{HH.mm|+02:00}}>
      ignore_unavailable: False
      include_global_state: True
      partial: False
      wait_for_completion: True
      skip_repo_fs_check: False
      disable_action: False
    filters:
      - filtertype: none

And I need to know why curator is checking for curator_get_datemath_function_qltizhfzalooqswfglbahsqtxsjoejwg-2018.12.11_08.39 index and what is it trying to do?
Any links would be helpful.

Thanks

Hi @Elango-mas,

Could you please confirm your curator version?

Please refer below thread where other user was facing same issue in 5.4.1. If you are using same version please upgrade it.

Regards,
Harsh

Hi Harsh,

I am using curator 5.6.

The reference you sent is not the problem i face. I have specified that my snapshot job is working fine.

Before doing the snapshot, it is trying to update the date to the snapshot name where i get this error.

Thanks!

This is expected behavior and nothing to be concerned about.

Curator performs a GET with a dummy index name in order to get date math calculations from Elasticsearch, rather than attempting to do the date math calculations in Curator.

Because you are in DEBUG logging, you see it happen. Otherwise you never would have known.

1 Like

Thank you theuntergeek !

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