CannedACL is not valid: ” + cannedACL + ” – Elasticsearch Error How To Solve Related Issues



CannedACL is not valid: ” + cannedACL + ” – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 

 

This guide will help you check for common problems that cause the log “cannedACL is not valid: ” + cannedACL + “” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: repositories, repository-s3, plugins.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”cannedACL is not valid: [” + cannedACL + “]”classname  is S3BlobStore.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (cur.toString().equalsIgnoreCase(cannedACL)) {
  return cur;
  }
  }
 
  throw new BlobStoreException("cannedACL is not valid: [" + cannedACL + "]");
  }
 
  static class Stats {
 
  final AtomicLong listCount = new AtomicLong();

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 No RegionEndpoint or ServiceURL configured -views 24,615 ,score 27

S3 putobject throwing Invalid URI: The format of the URI could not be determined -views   1,825



Find Configuration Errors

Analyze Now