Log Checking sha for – How To Solve Related Issues

Log Checking sha for – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0


[glossary_exclude]To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) [/glossary_exclude]

To troubleshoot log “Checking sha for” it’s important to understand a few problems related to Elasticsearch concepts task. See bellow important tips and explanations on these concepts

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")

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 what shasum: elasticsearch-5.0.0.deb.sha1: no properly formatted SHA1 checksum lines found means? 0.34 K 2

Elasticsearch SHA-1 not available   0.60 K


About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now