Hi again, > I asked our IT staff for assistance, but I don't expect an answer before > *Monday*, > i.e. Jenkins will be down until at least Monday noon.
As expected, my request was answered no sooner than Monday 09:50 a.m. I was supposed to have SSH access with sudo rights by then, but all I got was SSH access *without* sudo rights. (And our staff currently has no clue why this is the case.) So all I could do was to look around with read access and dictate shell commands to our IT staff which they then executed with a few hours delay. My first attempt: Replace the LDAP plugin 1.13 with the former version 1.12. Result: Nothing changed. Second attempt: While reading Friday's logfiles I noticed: ---- CRITICAL: Failed to install Display URL API hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/plugins/display-url-api/0.5/display-url-api.hpi (redirected to: http://ftp.halifax.rwth-aachen.de/jenkins/plugins/display-url-api/0.5/display-url-api.hpi) ---- Since our firewall blocks outgoing connections unless they are whitelisted (and ftp.halifax.rwth-aachen.de:80 is not whitelisted), this Jenkins plugin could not automatically be installed. It's a mere "dependency" plugin -- I installed/updated all other "feature" plugins through uploading them directly through Jenkins's web interface. And in today's logfiles, which reported on the latest attempt to start Jenkins, say: ---- CRITICAL: Failed to install mailer: One or more dependencies could not be resolved for mailer : display-url-api (0.2) CRITICAL: Failed to install maven-plugin: One or more dependencies could not be resolved for maven-plugin : mailer (1.7) CRITICAL: Failed to install dashboard-view: One or more dependencies could not be resolved for dashboard-view : maven-plugin (2.3) CRITICAL: Failed to install analysis-core: One or more dependencies could not be resolved for analysis-core : maven-plugin (2.9) CRITICAL: Failed to install pmd: One or more dependencies could not be resolved for pmd : maven-plugin (2.9), analysis-core (1.77) CRITICAL: Failed to install ldap: One or more dependencies could not be resolved for ldap : mailer (1.8) CRITICAL: Failed to install conditional-buildstep: One or more dependencies could not be resolved for conditional-buildstep : maven-plugin (2.8) CRITICAL: Failed to install parameterized-trigger: One or more dependencies could not be resolved for parameterized-trigger : conditional-buildstep (1.3.1) CRITICAL: Failed to install jobConfigHistory: One or more dependencies could not be resolved for jobConfigHistory : maven-plugin (2.0) CRITICAL: Failed to install cobertura: One or more dependencies could not be resolved for cobertura : maven-plugin (1.480.3) CRITICAL: Failed to install disk-usage: One or more dependencies could not be resolved for disk-usage : mailer (1.8) CRITICAL: Failed to install findbugs: One or more dependencies could not be resolved for findbugs : analysis-core (1.77), maven-plugin (2.9) CRITICAL: Failed to install git: One or more dependencies could not be resolved for git : mailer (1.17) CRITICAL: Failed to install gerrit: One or more dependencies could not be resolved for gerrit : git (1.0) ---- As you can see, "display-url-api" is the only thing that's actually missing, and many other plugins fall with it (including the one of which the absence leads to the exception below). I asked out IT staff to manually upload the missing plugin to Jenkins' plugin folder and restart the service. This should resolve this issue. Cheers, Franz -----Original Message----- From: Zieris, Franz [mailto:franz.zie...@fu-berlin.de] Sent: Friday, September 23, 2016 5:44 PM To: dpp-devel@lists.sourceforge.net Subject: [DPP-Devel] Jenkins not starting, Plugin update failed Hi there, I messed up our Jenkins setup, by trying to update our plugins (which I do regularly and it worked out fine every time so far). But now, Jenkins won't start, probably because of a bug in the new version in one of the updated plugins. You can see for yourself if you want [1]: hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /srv/jenkins/config.xml [...] Caused by: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /srv/jenkins/config.xml [...] Caused by: java.io.IOException: Unable to read /srv/jenkins/config.xml [...] Caused by: jenkins.util.xstream.CriticalXStreamException: hudson.security.LDAPSecurityRealm : hudson.security.LDAPSecurityRealm [...] Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException: hudson.security.LDAPSecurityRealm Unfortunately, I don't have SSH access to the machine (as it's centrally managed now). I asked our IT staff for assistance, but I don't expect an answer before *Monday*, i.e. Jenkins will be down until at least Monday noon. After this particular incident is resolved, I will work out a disaster plan with our IT, as rogue plugins are likely to happen again. Sorry guys, but at least Gerrit is still up. Franz [1] http://saros-build.imp.fu-berlin.de/jenkins/ ------------------------------------------------------------------------------ _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel ------------------------------------------------------------------------------ _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
