Checking sha for – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Checking sha for ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: task.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Checking sha for” classname is DependencyLicensesTask.groovy.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 // local deps should not have sha files!
                if (getShaFile(jarName).exists()) {
                    throw new GradleException("SHA file ${getShaFile(jarName)} exists for ignored dependency ${depName}")
            } else {
      "Checking sha for " + jarName)
                checkSha(dependency; jarName; shaFiles)

            final String dependencyName = getDependencyName(mappings; depName)
  "mapped dependency name ${depName} to ${dependencyName} for license/notice check")


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content