Upgraded to 2.8.1 and now cannot access SVN repositories - Possibly ssh-rsa issue

Bradley Moyer September 5, 2012

Error from run.sh Log:

Caused by: org.tmatesoft.svn.core.SVNException: svn: E210002: There was a problem while connecting to 192.168.253.58:22

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.svn.SVNSSHConnector.open(SVNSSHConnector.java:152)

at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77)

at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1252)

at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:168)

at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:117)

at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148)

at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:44)

at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetProperties.run(SvnRemoteGetProperties.java:46)

at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetProperties.run(SvnRemoteGetProperties.java:28)

at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)

at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1224)

at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:291)

at org.tmatesoft.svn.core.wc.SVNWCClient.doGetProperty(SVNWCClient.java:1129)

at org.tmatesoft.svn.core.javahl.SVNClientImpl.propertyGet(SVNClientImpl.java:1302)

... 18 more

Caused by: java.io.IOException: There was a problem while connecting to 192.168.253.58:22

at com.trilead.ssh2.Connection.connect(Connection.java:792)

at org.tmatesoft.svn.core.internal.io.svn.ssh.SshHost.openConnection(SshHost.java:205)

at org.tmatesoft.svn.core.internal.io.svn.ssh.SshHost.openSession(SshHost.java:145)

at org.tmatesoft.svn.core.internal.io.svn.ssh.SshSessionPool.openSession(SshSessionPool.java:81)

at org.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector.open(SVNSSHConnector.java:129)

... 31 more

Caused by: java.io.IOException: Key exchange was not finished, connection is closed.

at com.trilead.ssh2.transport.KexManager.getOrWaitForConnectionInfo(KexManager.java:92)

at com.trilead.ssh2.transport.TransportManager.getConnectionInfo(TransportManager.java:231)

at com.trilead.ssh2.Connection.connect(Connection.java:744)

... 35 more

Caused by: java.io.IOException: The server hostkey was not accepted by the verifier callback.

at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:538)

at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:760)

at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:475)

... 1 more

Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn: E215003: Host key ('192.168.253.58:22 <ssh-rsa>') can not be verified.

at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.verifyHostKey(DefaultSVNAuthenticationManager.java:563)

at org.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector$1.verifyServerHostKey(SVNSSHConnector.java:124)

at org.tmatesoft.svn.core.internal.io.svn.ssh.SshHost$1.verifyServerHostKey(SshHost.java:208)

at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:534)

... 3 more

2012-09-05 15:28:36,401 ERROR - Unable to initialise repository TurkeyShipping due to com.cenqua.fisheye.config.ConfigException:Could not access svn+ssh://ROCITuser@192.168.253.58/opt/svnroot/x3000/ : org.tigris.subversion.javahl.ClientException: svn: E210002: There was a problem while connecting to 192.168.253.58:22

com.cenqua.fisheye.config.ConfigException: Could not access svn+ssh://ROCITuser@192.168.253.58/opt/svnroot/x3000/ : org.tigris.subversion.javahl.ClientException: svn: E210002: There was a problem while connecting to 192.168.253.58:22

at com.cenqua.fisheye.svn.SvnRepositoryTester.pingAndValidateAccess(SvnRepositoryTester.java:157)

at com.cenqua.fisheye.svn.SvnRepositoryScanner.validateAccess(SvnRepositoryScanner.java:353)

at com.cenqua.fisheye.svn.SvnRepositoryScanner.validateRepository(SvnRepositoryScanner.java:265)

at com.cenqua.fisheye.rep.BaseRepositoryScanner.startRepository(BaseRepositoryScanner.java:430)

at com.cenqua.fisheye.rep.BaseRepositoryScanner.doSlurpTransaction(BaseRepositoryScanner.java:217)

at com.cenqua.fisheye.rep.BaseRepositoryScanner.ping(BaseRepositoryScanner.java:184)

at com.cenqua.fisheye.rep.BaseRepositoryEngine.doSlurp(BaseRepositoryEngine.java:92)

at com.cenqua.fisheye.rep.RepositoryEngine.slurp(RepositoryEngine.java:383)

at com.cenqua.fisheye.rep.ping.OneOffPingRequest.doRequest(OneOffPingRequest.java:28)

at com.cenqua.fisheye.rep.ping.PingRequest.process(PingRequest.java:67)

at com.cenqua.fisheye.rep.RepositoryHandle.processPingRequests(RepositoryHandle.java:138)

at com.cenqua.fisheye.rep.RepositoryHandle.queuePingRequest(RepositoryHandle.java:128)

at com.cenqua.fisheye.rep.ping.PingRequest.run(PingRequest.java:33)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

at java.lang.Thread.run(Thread.java:662)

Caused by: com.cenqua.fisheye.rep.RepositoryClientException: org.tigris.subversion.javahl.ClientException: svn: E210002: There was a problem while connecting to 192.168.253.58:22

at com.cenqua.fisheye.svn.SvnThrottledClient.propertyGet(SvnThrottledClient.java:176)

at com.cenqua.fisheye.svn.SvnRepositoryTester.pingAndValidateAccess(SvnRepositoryTester.java:145)

... 15 more

1 answer

1 accepted

0 votes
Answer accepted
Bradley Moyer September 5, 2012

I had to set the SVNKIT_VM_OPTIONS paramters and run <fisheye_home>/lib/svn/jsvn without the "--no-auth-cache" option and save permanently and then the connection to the svn repositores starting working.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events