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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Fisheye can't read ssh key

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.

3 answers

1 accepted

0 votes
Answer accepted

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.

I updated Git for Windows and it is working now.

0 votes

Hi Trevan,

The error

Warning: Identity file c:\FISHEYE_INST\data\auth\Repo not accessible: No such file or directory.

clearly explains the file c:\FISHEYE_INST\data\auth\Repo was not readable to the user running FishEye. I'm guessing that there were wrong permissions that were fixed when key pair was recreated. Can you let me know what FishEye version are you using? Just curious as the issue was fixed recently in FishEye 3.2.1 release: https://jira.atlassian.com/browse/FE-4984

Cheers,

No, that didn't seem to be what is happening. I actually deleted that old identity file and let Fisheye regenerate it. So it should have been able to read/write the file. Also, this error occurred over a weekend and the file had previously been working.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence Cloud

Share your Confluence Cloud experience for a chance to win $500!

Take our 5-minute survey to win a $500 Visa gift card! Are you currently using Confluence Cloud? We want to hear from you! Fill out this quick survey about your Confluence Cloud experience so we ...

293 views 5 14
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you