Jenkins fails to start with EnvelopeException error


Jenkins will not start up and the logs are displaying an error like:

com.cloudbees.jenkins.cjp.installmanager.EnvelopeException: Errors found 
at com.cloudbees.jenkins.cjp.installmanager.CJPPluginManager$1.createException( 
at com.cloudbees.jenkins.cjp.installmanager.CJPPluginManager$1.createException( 
at com.cloudbees.jenkins.plugins.updates.envelope.AbstractOutput.createException( 
at com.cloudbees.jenkins.plugins.updates.envelope.Validation$Error.get( 
at com.cloudbees.jenkins.cjp.installmanager.CJPPluginManager.loadPlugins( 
at com.cloudbees.jenkins.cjp.installmanager.CJPPluginManager.loadBundledPlugins( 
at hudson.PluginManager$1$ 
at org.jvnet.hudson.reactor.TaskGraphBuilder$ 
at org.jvnet.hudson.reactor.Reactor.runTask( 
at jenkins.model.Jenkins$5.runTask( 
at org.jvnet.hudson.reactor.Reactor$ 
at org.jvnet.hudson.reactor.Reactor$ 
at java.util.concurrent.ThreadPoolExecutor.runWorker( 
at java.util.concurrent.ThreadPoolExecutor$ 
Caused: org.jvnet.hudson.reactor.ReactorException 
at org.jvnet.hudson.reactor.Reactor.execute( 
at jenkins.model.Jenkins.executeReactor( 
at jenkins.model.Jenkins.<init>( 
at hudson.model.Hudson.<init>( 
at hudson.model.Hudson.<init>( 
at hudson.WebAppMain$ 
Caused: hudson.util.HudsonFailedToLoad 
at hudson.WebAppMain$



Usually this error will occur when the $JENKINS_HOME/cb-envelope/envelope.json file is corrupt or empty. To fix this, simply delete the entire $JENKINS_HOME/cb-envelope directory and restart Jenkins. This should prompt Jenkins to recreate the directory and corresponding files correctly on boot up and allow it to start successfully.

If after removing the cb-envelope directory and restarting your instance is still encountering this Envelope Exception error on startup then it is highly likely you have a misconfigured plugin. Please check your jenkins.log for any plugin related errors on startup, or $JENKINS_HOME/plugins directory for any unexpected plugins, custom or ‘SNAPSHOT’ plugins that may be stored there causing this error.

Specifically one error in your jenkins.log at startup that you may see indicating a misconfigured plugin which needed to be deleted/disabled would be as follows:

WARNING: Unable to list plugin <PLUGIN_JPI_PATH> Failed to expand <PLUGIN_JPI_PATH>

Any misconfigured or custom plugins should be disabled by adding touch ${PLUGIN_NAME}.jpi.disabled in this /plugins directory and then restart your instance once more.

Have more questions?


Please sign in to leave a comment.