Re: Upgrade to Jenkins 2 failed

2016-07-19 Thread Mingxing Tian
This is an FAQ. Solution is to disable AJP. See details in jira Quote from above link for reference JENKINS_AJP_PORT="-1" in /etc/sysconfig/jenkins solved problem https://stackoverflow.com/questions/38157686/migrating-to-jenkins-2-1-ajp-sup

Re: Upgrade to Jenkins 2 failed

2016-05-13 Thread Marcin Wieczorek
Ran into the same problem and finally found this: https://issues.jenkins-ci.org/browse/JENKINS-33776 That solved it for me. Marcin On Thursday, May 12, 2016 at 2:48:45 AM UTC-7, David Aldrich wrote: > > Hi > > I have tried to upgrade our Jenkins test server from 1.656 to 2.3 by > copying the

Re: Upgrade to Jenkins 2 failed

2016-05-13 Thread Stephen Connolly
When you upgrade if using the built in jetty the feature is removed in the newer code. If you were using AJP then you need to switch to Tomcat as your servlet container. On 13 May 2016 at 10:34, David Aldrich wrote: > > However, some of the native packages enabled it by default for no real > re

Re: Upgrade to Jenkins 2 failed

2016-05-13 Thread Daniel Beck
> On 13.05.2016, at 11:34, David Aldrich wrote: > > Please tell me how I would disable/remove it. Depends on how you installed Jenkins. https://wiki.jenkins-ci.org/display/JENKINS/Native+Packages should explain where the config file is. -- You received this message because you are subscribe

RE: Upgrade to Jenkins 2 failed

2016-05-13 Thread David Aldrich
> However, some of the native packages enabled it by default for no real reason, > and in that case it suffices to just disable/remove the option. Please tell me how I would disable/remove it. David -- You received this message because you are subscribed to the Google Groups "Jenkins Users"

Re: Upgrade to Jenkins 2 failed

2016-05-13 Thread Daniel Beck
> On 13.05.2016, at 10:15, David Aldrich wrote: > > Are there any hints on how to resolve this condition, i.e. where an AJP port > is used in a Jenkins 1.x installation, but we want upgrade to 2.x? If you're actually using AJP, follow Stephen's advice. However, some of the native packages e

Re: Upgrade to Jenkins 2 failed

2016-05-13 Thread Stephen Connolly
- > > From: jenkinsci-users@googlegroups.com [mailto:jenkinsci- > > us...@googlegroups.com] On Behalf Of Daniel Beck > > Sent: 12 May 2016 13:23 > > To: jenkinsci-users@googlegroups.com > > Subject: Re: Upgrade to Jenkins 2 failed > > > > > > &

RE: Upgrade to Jenkins 2 failed

2016-05-13 Thread David Aldrich
nsci-users@googlegroups.com [mailto:jenkinsci- > us...@googlegroups.com] On Behalf Of Daniel Beck > Sent: 12 May 2016 13:23 > To: jenkinsci-users@googlegroups.com > Subject: Re: Upgrade to Jenkins 2 failed > > > > On 12.05.2016, at 11:48, David Aldrich > wrote: > > > &g

RE: Upgrade to Jenkins 2 failed

2016-05-12 Thread David Aldrich
Hi Daniel > My guess is that your service config file defines an AJP port, which causes > startup to fail. See the 2.0 changelog. Thanks, I think you are correct: SEVERE: Container startup failed java.io.IOException: Failed to start a listener: winstone.Ajp13ConnectorFactory at winstone.

Re: Upgrade to Jenkins 2 failed

2016-05-12 Thread Daniel Beck
> On 12.05.2016, at 11:48, David Aldrich wrote: > > Any suggestions please? Check /var/log/jenkins/jenkins.log. My guess is that your service config file defines an AJP port, which causes startup to fail. See the 2.0 changelog. -- You received this message because you are subscribed to the