Since upgrading to Fisheye 2.8.1 we are seeing connection failures on all our SVN repositories

[Peter Nash]

Since upgrading Fisheye all the SVN repos are failing to connect with errors similar to the following:

Unable to initialise repository Configuration due to com.cenqua.fisheye.config.ConfigException:Could not access svn+ssh://svn.changeworks.local/var/local/subversion/configuration/ : org.tigris.subversion.javahl.ClientException: svn: E210002: There was a problem while connecting to svn.changeworks.local:22

In the Fisheye log we are seeing errors like:

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

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

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)

[Bradley Moyer · Accepted solution]

See also my solution at https://answers.atlassian.com/questions/84445/upgraded-to-2-8-1-and-now-cannot-access-svn-repositories-possibly-ssh-rsa-issue

-Bradley

[Peter Nash]

Runing "sh ./jsvn ls svn+ssh://repo_url" from fisheye/lib/svn as the fisheye service user (where repo_url is the repository) prompts for user name, password and then gives an option to permanently trust the connection (p).

[SimonS]

Hi Peter,

This looks like a SSH issue. You may want to try reimporting your keys per Fisheye's Authentication settings:

https://confluence.atlassian.com/display/FISHEYE/Authentication

Our support team will be able to help diagnose and debug the issue if fiddling with the keys doesn't work.

http://support.atlassian.com

-Simon