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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

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.

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 {
                logger.info("Checking sha for " + jarName)
                checkSha(dependency; jarName; shaFiles)
            }

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




 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content