[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator resolved JENKINS-24200 as Fixed All builds fail with E175002 With Daniel's help my server and slave nodes are all now behaving exactly as they should do. Change By: System Administrator (13/Aug/14 2:03 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator edited a comment on JENKINS-24200 All builds fail with E175002 Just so it's all written down here, a copy of my last note in the IRC chat: Well that was easier to find than I expected. http://docs.appdynamics.com/display/PRO14S/Tomcat+as+a+Windows+Service+Configuration shows how to add Java Options to Tomcat startup. I added -Djsse.enableSNIExtension=false to Java Options in the Configure Tomcat application and restarted the Apache Tomcat service, now it works perfectly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator commented on JENKINS-24200 All builds fail with E175002 Just so it's all writeen down here, a copy of my last note in the IRC chat: Well that was easier to find than I expected. http://docs.appdynamics.com/display/PRO14S/Tomcat+as+a+Windows+Service+Configuration shows how to add Java Options to Tomcat startup. I added -Djsse.enableSNIExtension=false to Java Options in the Configure Tomcat application and restarted the Apache Tomcat service, now it works perfectly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator edited a comment on JENKINS-24200 All builds fail with E175002 Success! Thank you very much. The certificate on Subversion was issued by our CA so I don't think that applies, however I did get one slave to build just now by adding the -Djsse.enableSNIExtension=false argument in to the slave.xml file in C:\Jenkins_Slave_Home. -Xrs -Djsse.enableSNIExtension=false -jar "%BASE%\slave.jar"... That looks like it'll get the jobs running again to me, I'll apply it to the other slaves but when I go to configure the job in Jenkins it still gives me E175002 as shown above, despite it then working on the slave. Do you know how I can apply the same fix to my Jenkins server? I don't see a java.exe process so I'm thinking that's different? (Edit: all jobs now work so I'm down to Jenkins reporting an error in the job configuration page.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
Daniel Beck commented on JENKINS-24200 All builds fail with E175002 Jenkins.xml in Jenkins home, or in /etc/defaults or /etc/sysconfig depending on OS. For future requests for assistance, please try the mailing lists or IRC first. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator commented on JENKINS-24200 All builds fail with E175002 Success! Thank you very much. The certificate on Subversion was issued by our CA so I don't think that applies, however I did get one slave to build just now by adding the -Djsse.enableSNIExtension=false argument in to the slave.xml file. -Xrs -Djsse.enableSNIExtension=false -jar "%BASE%\slave.jar"... That looks like it'll get the jobs running again to me, I'll apply it to the other slaves but when I go to configure the job in Jenkins it still gives me E175002 as shown above, despite it then working on the slave. Do you know how I can apply the same fix to my Jenkins server? I don't see a java.exe process so I'm thinking that's different? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
Daniel Beck commented on JENKINS-24200 All builds fail with E175002 This may also be worth a try: http://www.visualsvn.com/support/topic/00056/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
Daniel Beck commented on JENKINS-24200 All builds fail with E175002 The lines starting with "at" and "Caused by" are the full stack trace http://stackoverflow.com/a/14884941 Did you try this? The -D... parameters must occur before the -jar argument to the java call. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator edited a comment on JENKINS-24200 All builds fail with E175002 Bear with me, I'm figuring this out since the person who set it up left... Where is the 'full stack trace'? I have Jenkins 1.565.1 running on Windows Server 2008 R2. If I try to configure a job the Source Code Management section says (despite the credentials working fine outside Jenkins): org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /svn/ failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99) at hudson.scm.SubversionSCM$DescriptorImpl.checkRepositoryPath(SubversionSCM.java:2288) at hudson.scm.SubversionSCM$ModuleLocation$DescriptorImpl.doCheckCredentialsId(SubversionSCM.java:2997) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.R
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator commented on JENKINS-24200 All builds fail with E175002 Bear with me, I'm figuring this out since the person who set it up left... Where is the 'full stack trace'? I have Jenkins 1.565.1 running on Windows Server 2008 R2. If I try to configure a job the Source Code Management section says: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /svn/ failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99) at hudson.scm.SubversionSCM$DescriptorImpl.checkRepositoryPath(SubversionSCM.java:2288) at hudson.scm.SubversionSCM$ModuleLocation$DescriptorImpl.doCheckCredentialsId(SubversionSCM.java:2997) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilte
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
Daniel Beck commented on JENKINS-24200 All builds fail with E175002 Please include the full stack trace for the error message. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator edited a comment on JENKINS-24200 All builds fail with E175002 I upgraded Visual SVN Server to 2.7.7 and now I get this error on every job in Jenkins. I am able to check projects out with TortoiseSVN, I am able to log in to the Visual SVN website directly through a browser. I have a Windows Server with the Jenkins site on. If I try to configure the job to check files out I get this error message when supplying credentials. I've tried via the Job Configuration page and the Credentials page. The slave nodes are unable to checkout either. I have seen suggestions to add -Dsvnkit.http.sslProtocols="SSLv3 to the service, it said to add it to the jar command but the service on the slave nodes is an executable. I followed some instructions and added it to the slave config XML, that didn't work. (http://www.tikalk.com/alm/jenkins-svn-integration-bugs-and-workarounds) When I do svn checkout I can check the files out but I don't get asked about a certificate. (I'm using the SVN from Tortoise for that.) Some suggest running svn from the command line but the machines don't have it without installing something like TortoiseSVN. I tried installing Tortoise and running it from there, I got the Subversion\auth folder they were talking about but it still doesn't work. Another said to modify the subversion config but didn't say where that is. Any helpful suggestions gratefully received, if you need more info let me know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator edited a comment on JENKINS-24200 All builds fail with E175002 I upgraded Visual SVN Server to 2.7.7 and now I get this error on every job in Jenkins. I am able to check projects out with TortoiseSVN, I am able to log in to the Visual SVN website directly through a browser. I have a Windows Server with the Jenkins site on. If I try to configure the job to check files out I get this error message when supplying credentials. I've tried via the Job Configuration page and the Credentials page. The slave nodes are unable to checkout either. I have seen suggestions to add -Dsvnkit.http.sslProtocols="SSLv3 to the service, it said to add it to the jar command but the service on the slave nodes is an executable. I followed some instructions and added it to the slave config XML, that didn't work. (http://www.tikalk.com/alm/jenkins-svn-integration-bugs-and-workarounds) When I do svn checkout I can check the files out but I don't get asked about a certificate. Some suggest running svn from the command line but the machines don't have it. I tried installing Tortoise and running it from there, I got the Subversion\auth folder they were talking about but it still doesn't work. Another said to modify the subversion config but didn't say where that is. Any helpful suggestions gratefully received, if you need more info let me know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator commented on JENKINS-24200 All builds fail with E175002 I upgraded Visual SVN Server to 2.7.7 and now I get this error on every job in Jenkins. I am able to check projects out with TortoiseSVN, I am able to log in to the Visual SVN website directly through a browser. I have a Windows Server with the Jenkins site on. If I try to configure the job to check files out I get this error message when supplying credentials. I've tried via the Job Configuration page and the Credentials page. The slave nodes are unable to checkout either. I have seen suggestions to add -Dsvnkit.http.sslProtocols="SSLv3 to the service, it said to add it to the jar command but the service on the slave nodes is an executable. I followed some instructions and added it to the slave config XML, that didn't work. (http://www.tikalk.com/alm/jenkins-svn-integration-bugs-and-workarounds) Some suggest running svn from the command line but the machines don't have it. I tried installing Tortoise and running it from there, I got the Subversion\auth folder they were talking about but it still doesn't work. Another said to modify the subversion config but didn't say where that is. Any helpful suggestions gratefully received, if you need more info let me know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator created JENKINS-24200 All builds fail with E175002 Issue Type: Bug Assignee: Unassigned Components: subversion Created: 11/Aug/14 1:57 PM Description: ERROR: Failed to check out org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS failed None of the suggestions I've seen is any help. Environment: Windows Project: Jenkins Priority: Major Reporter: System Administrator This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
