[JIRA] [subversion] (JENKINS-23761) "No route to host" in scm access for multi-conf jobs

[henri.go...@gmail.com (JIRA)]

Henri Gomez
 updated  JENKINS-23761


"No route to host" in scm access for multi-conf jobs
















Change By:


Henri Gomez
(11/Jul/14 4:18 PM)




Affects Version/s:


current





Environment:


Jenkins LTS 1.544.3, Subversion Plugin 2.4, CollabNet 4.0.10 (SSL)
.



























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-23761) "No route to host" in scm access for multi-conf jobs

[henri.go...@gmail.com (JIRA)]

Henri Gomez
 created  JENKINS-23761


"No route to host" in scm access for multi-conf jobs















Issue Type:


Bug



Assignee:


Unassigned


Components:


subversion



Created:


11/Jul/14 4:17 PM



Description:


I get more and more random errors on multi-conf jobs where many slaves are triggered at same time to build native packages (freestyle).


at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:706)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:14)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:9)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238)
	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
	at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:777)
	at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:99)
	... 14 more
Caused by: svn: E175002: OPTIONS /svn/ecd-catalog/trunk/cifortify-sca failed
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
	... 34 more
Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS request failed on '/svn/ecd-catalog/trunk/cifortify-sca'
svn: E175002: No route to host
	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:777)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382)
	... 33 more
Caused by: svn: E175002: OPTIONS request failed on '/svn/ecd-catalog/trunk/cifortify-sca'
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:775)
	... 34 more
Caused by: svn: E175002: No route to host
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:109)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:528)
	... 34 more
Caused by: java.net.NoRouteToHostException: No route to host
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
	at java.net.Socket.connect(Socket.java:529)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:570)
	at org.tmatesoft.svn.core.internal.util.SVNSocketConnection.run(SVNSocketConnection.java:57)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
	... 5 more
Finished: FAILURE


Of course host is up and accessible from slaves.

I did svn checkout directly from slaves using native svn 1.7 without problems.

Subversion server is using CollabNet 4.0.10 and SSL (using valid certificate).

I tried various SVN operations (forcing checkout, update) but no more luck.

This is a serious show stopper especially by its randomly nature, ie on 10 slaves, only one will be in trouble.






Environment:


Jenkins LTS 1.544.3, Subversion Plugin 2.4, CollabNet 4.0.10 (SSL)




Project:


Jenkins



Priority:


Major