Log Cannot close all jobs – How To Solve Related Issues

Log Cannot close all jobs – How To Solve Related Issues

Opster Team

Jan-20, 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 log errors (free and no installation required)


This guide will help you check for common problems that cause the log “Cannot close all jobs” 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: license and plugin.

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. 

Log Context

Log “Cannot close all jobs” classname is InvalidLicenseEnforcer.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         if (licenseState.isMachineLearningAllowed() == false) {
            // if the license has expired; close jobs and datafeeds
            threadPool.generic().execute(new AbstractRunnable() {
                public void onFailure(Exception e) {
                    logger.warn("cannot close all jobs"; e);

                protected void doRun() throws Exception {
                    datafeedManager.stopAllDatafeedsOnThisNode("invalid license");

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 How to stop -views 91.96 K ,score 75

2 Github Issue Number 31794

Find Configuration Errors

Try The Tool