Issue
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(CJPPluginManager.java:75)
at com.cloudbees.jenkins.cjp.installmanager.CJPPluginManager$1.createException(CJPPluginManager.java:72)
at com.cloudbees.jenkins.plugins.updates.envelope.AbstractOutput.createException(AbstractOutput.java:36)
at com.cloudbees.jenkins.plugins.updates.envelope.Validation$Error.get(Validation.java:273)
at com.cloudbees.jenkins.cjp.installmanager.CJPPluginManager.loadPlugins(CJPPluginManager.java:236)
at com.cloudbees.jenkins.cjp.installmanager.CJPPluginManager.loadBundledPlugins(CJPPluginManager.java:215)
at hudson.PluginManager$1$1.run(PluginManager.java:383)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)
at jenkins.model.Jenkins$5.runTask(Jenkins.java:1083)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused: org.jvnet.hudson.reactor.ReactorException
at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:282)
at jenkins.InitReactorRunner.run(InitReactorRunner.java:48)
at jenkins.model.Jenkins.executeReactor(Jenkins.java:1117)
at jenkins.model.Jenkins.<init>(Jenkins.java:921)
at hudson.model.Hudson.<init>(Hudson.java:85)
at hudson.model.Hudson.<init>(Hudson.java:81)
at hudson.WebAppMain$3.run(WebAppMain.java:233)
Caused: hudson.util.HudsonFailedToLoad
at hudson.WebAppMain$3.run(WebAppMain.java:250)
Environment
- CloudBees CI (CloudBees Core)
- CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller
- CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
- CloudBees CI (CloudBees Core) on traditional platforms - Client controller
- CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
- CloudBees Jenkins Enterprise
- CloudBees Jenkins Enterprise - Managed controller
- CloudBees Jenkins Enterprise - Operations Center
- CloudBees Jenkins Platform - Client controller
- CloudBees Jenkins Platform - Operations Center
- CloudBees Jenkins Distribution
Resolution
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>
java.io.IOException: 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.
0 Comments