Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33776

Cannot start from preview rpm

XMLWordPrintable

      I installed the rpm from the preview repository and simply started it, but get this in the log:
      Running from: /usr/lib/jenkins/jenkins.war
      Mar 24, 2016 3:55:27 AM org.eclipse.jetty.util.log.JavaUtilLog info
      INFO: Logging initialized @1015ms
      Mar 24, 2016 3:55:27 AM winstone.Logger logInternal
      INFO: Beginning extraction from war file
      Mar 24, 2016 3:55:28 AM org.eclipse.jetty.util.log.JavaUtilLog warn
      WARNING: Empty contextPath
      Mar 24, 2016 3:55:29 AM winstone.Logger logInternal
      INFO: Winstone shutdown successfully
      Mar 24, 2016 3:55:29 AM winstone.Logger logInternal
      SEVERE: Container startup failed
      java.io.IOException: Failed to start a listener: winstone.Ajp13ConnectorFactory
      at winstone.Launcher.spawnListener(Launcher.java:207)
      at winstone.Launcher.<init>(Launcher.java:148)
      at winstone.Launcher.main(Launcher.java:352)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:497)
      at Main._main(Main.java:246)
      at Main.main(Main.java:91)
      Caused by: java.lang.UnsupportedOperationException: AJP support is removed in Winstone 3.0 due to Jetty 9 not supporting AJP. For reverse proxying, please use HTTP instead of AJP.
      at winstone.Ajp13ConnectorFactory.start(Ajp13ConnectorFactory.java:31)
      at winstone.Launcher.spawnListener(Launcher.java:205)
      ... 8 more

      The issue does not go away when downgrading Java to java version "1.7.0_95"

        1. beta1.patch
          2 kB

          [JENKINS-33776] Cannot start from preview rpm

          Bent Terp created issue -

          Daniel Beck added a comment -

          Is this a new installation, or an upgrade?

          Could you try the beta which we released earlier today?

          Daniel Beck added a comment - Is this a new installation, or an upgrade? Could you try the beta which we released earlier today?
          Daniel Beck made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]

          Bent Terp added a comment -

          There is no new version available on the jenkins-rc repo:
          [centos@jenkins ~]$ sudo yum list jenkins
          Loaded plugins: fastestmirror
          Loading mirror speeds from cached hostfile

          • base: ftp.lysator.liu.se
          • extras: ftp.lysator.liu.se
          • updates: ftp.lysator.liu.se
            Installed Packages
            jenkins.noarch 2.0-1.1 @jenkins-rc

          I can't see which build it corresponds to.

          Bent Terp added a comment - There is no new version available on the jenkins-rc repo: [centos@jenkins ~] $ sudo yum list jenkins Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile base: ftp.lysator.liu.se extras: ftp.lysator.liu.se updates: ftp.lysator.liu.se Installed Packages jenkins.noarch 2.0-1.1 @jenkins-rc I can't see which build it corresponds to.

          Daniel Beck added a comment -

          Probably just caused by our release process that does not support multiple alphas etc. and reuses/replaces versions. This is the first time we don't just increment a number on a weekly basis, and it shows

          If you look at http://pkg.jenkins-ci.org/redhat-rc/ it was last updated this Thursday.

          Daniel Beck added a comment - Probably just caused by our release process that does not support multiple alphas etc. and reuses/replaces versions. This is the first time we don't just increment a number on a weekly basis, and it shows If you look at http://pkg.jenkins-ci.org/redhat-rc/ it was last updated this Thursday.
          Bent Terp made changes -
          Attachment New: beta1.patch [ 32287 ]

          Bent Terp added a comment -

          The sysconfig contains
          JENKINS_AJP_PORT="8009"
          JENKINS_AJP_LISTEN_ADDRESS=""
          and that triggers the behaviour.

          If I comment out those two lines, then it works much better.

          If AJP is no longer supported (which is what java -jar jenkins.war --help indicates to me), then AJP should be removed from sysconfig and init-script. It is a debatable point whether jenkins should ignore those parameters rather than crash, but it is a rather heavy-fisted way of telling people to update their installation. Probably the code has not been completely removed yet.

          Anyways, the fix seems simple - suggestion attached as beta1.patch

          Thanks for reaching out!

          Bent Terp added a comment - The sysconfig contains JENKINS_AJP_PORT="8009" JENKINS_AJP_LISTEN_ADDRESS="" and that triggers the behaviour. If I comment out those two lines, then it works much better. If AJP is no longer supported (which is what java -jar jenkins.war --help indicates to me), then AJP should be removed from sysconfig and init-script. It is a debatable point whether jenkins should ignore those parameters rather than crash, but it is a rather heavy-fisted way of telling people to update their installation. Probably the code has not been completely removed yet. Anyways, the fix seems simple - suggestion attached as beta1.patch Thanks for reaching out!

          Daniel Beck added a comment -

          Native packaging needs to be adapted to no longer use the AJP connector. Ideally, Winstone will not fail so hard but just log a warning otherwise.

          https://github.com/jenkinsci/packaging/blob/master/rpm/build/SOURCES/jenkins.sysconfig.in#L110
          https://github.com/jenkinsci/packaging/blob/master/rpm/build/SOURCES/jenkins.init.in#L91...L92

          https://github.com/jenkinsci/packaging/blob/master/suse/build/SOURCES/jenkins.sysconfig.in#L77
          https://github.com/jenkinsci/packaging/blob/master/suse/build/SOURCES/jenkins.init.in#L82

          https://github.com/jenkinsci/packaging/blob/master/deb/build/debian/jenkins.default#L60
          https://github.com/jenkinsci/packaging/blob/master/deb/build/debian/jenkins.default#L69
          https://github.com/jenkinsci/packaging/blob/master/deb/build/debian/jenkins.default#L75

          Daniel Beck added a comment - Native packaging needs to be adapted to no longer use the AJP connector. Ideally, Winstone will not fail so hard but just log a warning otherwise. https://github.com/jenkinsci/packaging/blob/master/rpm/build/SOURCES/jenkins.sysconfig.in#L110 https://github.com/jenkinsci/packaging/blob/master/rpm/build/SOURCES/jenkins.init.in#L91...L92 https://github.com/jenkinsci/packaging/blob/master/suse/build/SOURCES/jenkins.sysconfig.in#L77 https://github.com/jenkinsci/packaging/blob/master/suse/build/SOURCES/jenkins.init.in#L82 https://github.com/jenkinsci/packaging/blob/master/deb/build/debian/jenkins.default#L60 https://github.com/jenkinsci/packaging/blob/master/deb/build/debian/jenkins.default#L69 https://github.com/jenkinsci/packaging/blob/master/deb/build/debian/jenkins.default#L75
          Daniel Beck made changes -
          Component/s New: packaging [ 20120 ]
          Component/s New: winstone-jetty [ 20645 ]
          Component/s Original: core [ 15593 ]
          Daniel Beck made changes -
          Priority Original: Critical [ 2 ] New: Blocker [ 1 ]

            svanoort Sam Van Oort
            bentterp Bent Terp
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: