Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Fisheye 2.8 svn+ssh connections fail

Dan Wilson August 15, 2012

Just upgraded to fisheye 2.8 and now all the connections to my repositories fail with the following error in the debug log:

Caused by: java.io.IOException: There was a problem while connecting to svn.wfrmls.com: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 ('svn.wfrmls.com: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)

Anyone else seeing this or have a solution?

2 answers

1 accepted

0 votes
Answer accepted
Norman Abramovitz
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 22, 2012

I would first check to see if your host key somehow changed based upon the message above since it unclear what fisheye is using for its ssh interface to figure out if incompatabilies exist.

I would next check that all the parameters are being passed as expected. I could not tell which svnkit and ssh versions are supported at the fisheye 2.8 version verses the previous versions. I suspect there was a change there as noted in the following url.

https://confluence.atlassian.com/pages/viewpage.action?pageId=166529059

If you setup a new test respository, does that fail as well? If so and you feel it is not your parameters, then contact Altassian support.

Thomas Trostel August 22, 2012

Yes a new repository fails ... the URL noted doesn't help either but thanks for trying. The host key has not changed. The parameters being passed by the previous version of FishEye and the new ones are identical ... I double checked.

Dan Wilson August 22, 2012

I was able to get mine working by running the jsvn command indicated in the above confluence link. By running it manually, it showed that my server was untrusted. It allowed me to trust the server permanently and everything started working properly.

The upgrade must have put some additional checks in place (or wiped out the ssh cache).

0 votes
Thomas Trostel August 22, 2012

Yes,

I have the same problem on my server.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events