Open timja opened 8 years ago
How is this one different to JENKINS-33773 ?
danielbeck ...
Ok, I can reproduce this, but only if I do NOT go into the global config and save it.
Here's a recording of my run through the above instructions (including opening and saving the global config) ... https://youtu.be/wZpZtELA9Cc
As I say, if I just run 1.532.3 on a clean JENKINS_HOME, kill it and then run 2.0-beta2 (no config save), then I do the the error you showed above.
And I note that in the above situation, when I access Jenkins, I am brought to the install wizard (and the key is printed on the console).
My RHEL5 Linux, Jenkins 2.23 revision, has this same issue. Does anyone know what context path (Line 8) is being referred to or how to eliminate this warning?
1 Running from: /data/jenkins/jenkins.war
2 webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
3 Sep 20, 2016 1:59:15 PM org.eclipse.jetty.util.log.JavaUtilLog info
4 INFO: Logging initialized @811ms
5 Sep 20, 2016 1:59:15 PM winstone.Logger logInternal
6 INFO: Beginning extraction from war file
7 Sep 20, 2016 1:59:15 PM org.eclipse.jetty.util.log.JavaUtilLog warn
8 WARNING: Empty contextPath
9 Sep 20, 2016 1:59:15 PM org.eclipse.jetty.util.log.JavaUtilLog info
10 INFO: jetty-9.2.z-SNAPSHOT
11 Sep 20, 2016 1:59:16 PM org.eclipse.jetty.util.log.JavaUtilLog info
12 INFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
13 Jenkins home directory: /data/jenkins found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
14 Sep 20, 2016 1:59:17 PM org.eclipse.jetty.util.log.JavaUtilLog info
15 INFO: Started w.@3c77d488
{/,file:/data/jenkins/war/,AVAILABLE} {/data/jenkins/war}
16 Sep 20, 2016 1:59:17 PM org.eclipse.jetty.util.log.JavaUtilLog info
17 INFO: Started ServerConnector@470734c3
{HTTP/1.1} {0.0.0.0:8080}
18 Sep 20, 2016 1:59:17 PM org.eclipse.jetty.util.log.JavaUtilLog info
19 INFO: Started @2777ms
wilson_ds_net Ignore it. Doesn't mean anything.
Steps to reproduce
Expected result
Upgrading works.
Actual result
Jenkins spews warnings
Not sure what the circumstances are for this to happen.
Originally reported by danielbeck, imported from: Errors after upgrading Jenkins from "1.0" to 2.0-beta-2