[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title Daniel Beck commented on JENKINS-62164 Re: Error after update to 2.222.3 with pinned plugins (Note that this feature was in fact removed, my previous response might give the wrong impression – internal APIs remain but behave as nothing is ever pinned.) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206093.1588685014000.22208.1588714380190%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title Daniel Beck closed an issue as Cannot Reproduce The error doesn't look related to pinning. My best guess is extraction of the war file failed, and trying again, perhaps with fewer files / more free disk space, worked. Jenkins / JENKINS-62164 Error after update to 2.222.3 with pinned plugins Change By: Daniel Beck Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title ickersep edited a comment on JENKINS-62164 Re: Error after update to 2.222.3 with pinned plugins I discovered that I have several pinned plugins (all with timestamps from 4-5 years ago). After I removed all the *.pinned files Jenkins starts again. This is strange since [https://wiki.jenkins.io/display/JENKINS/Pinned+Plugins] mentions that the pinned plugins feature was removed in Jenkins 2, so I wouldn't have expected that this suddenly causes problems. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206093.1588685014000.21989.1588686840044%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title ickersep commented on JENKINS-62164 Re: Error after update to 2.222.3 with pinned plugins I discovered that I have several pinned plugins (all with timestamps from 4-5 years ago). After I removed all the *.pinned files Jenkins starts again. This is strange since https://wiki.jenkins.io/display/JENKINS/Pinned+Plugins mentions that the pinned plugins feature was removed in Jenkins 2, so I wouldn't have expected that this suddenly causes problems. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206093.1588685014000.21988.1588686780043%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title ickersep updated an issue Jenkins / JENKINS-62164 Error after update to 2.222.3 with pinned plugins Change By: ickersep Summary: Error after update to 2.222.3 with pinned plugins Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206093.1588685014000.21987.1588686660065%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3
Title: Message Title
ickersep updated an issue
Jenkins / JENKINS-62164
Error after update to 2.222.3
Change By:
ickersep
After upgrading to 2.222.3 (from 2. 2 204 . 04. 2) Jenkins fails to load properly and displays this error:{{java.lang.NoClassDefFoundError: Could not initialize class hudson.model.Hudson$MasterComputer}} \ {{ at jenkins.model.Jenkins.createComputer(Jenkins.java:3106)}} \ {{ at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:136)}} \ {{ at hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:47)}} \ {{ at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:210)}} \ {{ at hudson.model.Queue._withLock(Queue.java:1399)}} \ {{ at hudson.model.Queue.withLock(Queue.java:1276)}} \ {{ at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:196)}} \ {{ at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1617)}} \ {{ at jenkins.model.Jenkins.(Jenkins.java:998)}} \ {{ at hudson.model.Hudson.(Hudson.java:85)}} \ {{ at hudson.model.Hudson.(Hudson.java:81)}} \ {{ at hudson.WebAppMain$3.run(WebAppMain.java:233)}}{{Caused: hudson.util.HudsonFailedToLoad}} \ {{ at hudson.WebAppMain$3.run(WebAppMain.java:247)}} {{$ java -version}}{{java version "1.8.0_201"}}{{Java(TM) SE Runtime Environment (build 1.8.0_201-b09)}}{{Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)}}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62164) Error after update to 2.222.3
Title: Message Title
ickersep created an issue
Jenkins / JENKINS-62164
Error after update to 2.222.3
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2020-05-05 13:23
Environment:
Ubuntu 18.04
Priority:
Major
Reporter:
ickersep
After upgrading to 2.222.3 (from 2.2.04.2) Jenkins fails to load properly and displays this error: java.lang.NoClassDefFoundError: Could not initialize class hudson.model.Hudson$MasterComputer {{ at jenkins.model.Jenkins.createComputer(Jenkins.java:3106)}} {{ at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:136)}} {{ at hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:47)}} {{ at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:210)}} {{ at hudson.model.Queue._withLock(Queue.java:1399)}} {{ at hudson.model.Queue.withLock(Queue.java:1276)}} {{ at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:196)}} {{ at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1617)}} {{ at jenkins.model.Jenkins.(Jenkins.java:998)}} {{ at hudson.model.Hudson.(Hudson.java:85)}} {{ at hudson.model.Hudson.(Hudson.java:81)}} {{ at hudson.WebAppMain$3.run(WebAppMain.java:233)}} Caused: hudson.util.HudsonFailedToLoad {{ at hudson.WebAppMain$3.run(WebAppMain.java:247)}} $ java -version java version "1.8.0_201" Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
