Fisheye can't read ssh key

Trevan Richins

A few days ago, fisheye stopped indexing our repositories. When I run test connection, it gives a wierd message about it not being able to create the .ssh directory and that the identity file is not accessible. I've gone through the UI and recreated the ssh key and it can read and write it. The .ssh directory was originally created by fisheye and it hasn't changed. Any idea what's wrong?

Fisheye is using 'C:\Git\bin\ssh.exe' to authenticate with SSH authenticated repositories.

Error testing connection.
Error talking to repository:

Warning: Identity file c:\FISHEYE_INST\data\auth\Repo not accessible: No such file or directory.
Could not create directory 'u/.ssh'.
Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
fatal: The remote end hung up unexpectedly

at com.atlassian.fisheye.git.GitScmConfig.testConnection(GitScmConfig.java:143)
at com.cenqua.fisheye.RepositoryConfig.testConnection(RepositoryConfig.java:444)
at com.atlassian.fisheye.spi.admin.impl.DefaultRepositoryAdminService.testConnectionFor(DefaultRepositoryAdminService.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

Connection failed.

Trevan Richins

Updating Git actually didn't fix it. It happened a few hours after the update. The reason why it looked like it fixed it was because there was a long running ssh command going that had to be killed to update Git. When the error occurred again, I just killed that long running ssh command and it worked again.

I believe what actually happened was I had changed the number of "Incremental Indexing Threads" from 1 to 3 a few days earlier. I changed that back to 1 and I've never seen the longing running ssh command or this error since.