I'm seeing CrashLoopBackOff error whilst running curator job. Logs state "Failed to verify all nodes have repository access".
The cron job has been running without problem until the last few days.
Action file extract is as follows :-
2:
action: snapshot
description: "Snapshot indices to S3 older than one day"
options:
repository: s3
name: curator-%Y%m%d%H%M%S
ignore_unavailable: False
include_global_state: True
partial: False
wait_for_completion: True
skip_repo_fs_check: False
filters:
- filtertype: pattern
kind: prefix
value: logstash-
- filtertype: age
source: creation_date
direction: older
unit: days
unit_count: 1
All master and data nodes must have the S3 plugin installed, and have write access to the bucket. This step attempts to write to and read from the repository from each node. If one node fails (or times out), you will get that error.
If you know it's working, it could simply be a timeout error. In such case, you can use the skip_repo_fs_check option.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.