Fisheye clear cache index cache

Hey Guys,

Did you known how to clear repo index cache ?? I got following problem when someone or me add new SVN repo ( when repo is on git it work's perfect)  to fisheye using different credentials than special created by me "fishey" it come out with error unable to access regardless is that that different user had access to all root directory, already try clear index at server and at application site " maintenance tab"


Thank in advice for all hint and help 



1 answer

0 votes

Hi @Marcin Wilczynski,

Are you accessing those svn repositories locally (via file:/// protocol) or remotely (via either svn, svn+ssh or http(s)) protocols?  

In the former case you need to ensure file level permissions are sufficient so the user fisheye application is run by have full read access to the local repository.

In the latter case you may want to try accessing remote repository with the same credentials from command line to double check credentials are correct.  Also, may want to check application log (stored in <<FISHEYE_INST>>/var/log/ folder) to find out more details.

Hope that helps,

sorry forgot to add it, I'm accessing repo remotely via password and username, also already try add permission to full repo but got the same error sad at log nothing what could be important the same error : access forbidden. Credentials are correct smile check it couple times.

Depending on the version of FishEye you are using, there was a problem affecting pre 2.10 versions where many repositories were indexed from the same remote host:

2.10 and newer versions should cope with this correctly, but you need to ensure you specify the username in repository URL, e.g. e.g., see comment.

Do you think it might be the case, do you have many repositories indexed from the same remote host with different credentials?

The other reason I can think of is some network configuration, prohibiting access to svn repository from the machine FishEye is hosted on.  Do you want to try connecting using command line svn from the same machine perhaps, to verify?  

Another thing you can try is checking the logs on the svn repository side.  Perhaps you can verify there FishEye is hitting this server (so there is nothing on the network preventing communication) and using the credentials you expect FishEye to use?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Jan 15, 2019 in Statuspage

Introducing Statuspage Getting Started guides! First up: What is Statuspage?

Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...

297 views 5 2
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you