[
https://issues.jenkins-ci.org/browse/JENKINS-8847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161723#comment-161723
]
lars Nordin commented on JENKINS-8847:
--------------------------------------
Can you add some sort of monitoring that the DNS resolving doesn't have
intermittent issues via a DNS test script running that/those slaves?
> SVN error: path not found: 404 Not Found (http://svnhost.com) while
> checking-out code on slaves
> -----------------------------------------------------------------------------------------------
>
> Key: JENKINS-8847
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8847
> Project: Jenkins
> Issue Type: Bug
> Components: master-slave, subversion
> Environment: Linux 64 bit, java 1.6 64 bit, Hudson 1.393, SVN plug-in
> Hudson Subversion Plug-in 1.23
> Reporter: Jyothi Prakash Polani
> Priority: Critical
>
> We have a Hudson Master with couple of slaves. As per the configuration
> everything is alright and clocks are also in sync. However while check-in out
> the sources from subversion, it is failing with below log. this behavior is
> happening both the slaves but in an unpredictable manner. When this occurs,
> the only way I can run the jobs on the same slave is to restart the slave
> agent.
> Started by user XXXXXXX
> Building remotely on Slave1.mydomain.net
> Updating http://svnhost.com/svn/repos/MyProject
> ERROR: Failed to update http://svnhost.com/svn/repos/MyProject
> org.tmatesoft.svn.core.SVNException: svn: '/svn/repos/MyProject' path not
> found: 404 Not Found (http://svnhost.com)
> at
> org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
> at
> org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:624)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:275)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:263)
> at
> org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:516)
> at
> org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:98)
> at
> org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1001)
> at
> org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryUUID(DAVRepository.java:146)
> at
> org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:342)
> at
> org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:330)
> at
> org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:535)
> at
> org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:401)
> at
> hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:129)
> at
> hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:137)
> at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:725)
> at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:706)
> at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:690)
> at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1925)
> at hudson.remoting.UserRequest.perform(UserRequest.java:114)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:270)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at hudson.remoting.Engine$1$1.run(Engine.java:58)
> at java.lang.Thread.run(Thread.java:619)
> Please can some address this ?
> Thanks,
> Jyothi Polani
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
