com.cenqua.fisheye.config.ConfigException: Unable to get git version

upgraded to latest version FeCru 3.6.3 facing error while starting server

2015-01-15 16:05:44,891 WARN  - Problem starting repository Flap-Adserver

com.cenqua.fisheye.config.ConfigException: Unable to get git version

        at com.atlassian.fisheye.git.client.GitContext.determineGitVersion(GitCo

        at com.atlassian.fisheye.git.client.GitContext.determineGitVersion(GitCo

        at com.atlassian.fisheye.git.GitRepositoryEngine.ensureCorrectScmVersion


        at com.cenqua.fisheye.rep.BaseRepositoryEngine.doStart(BaseRepositoryEng

        at com.cenqua.fisheye.rep.RepositoryEngine.start(




        at com.cenqua.fisheye.config.DefaultRepositoryManager.runRepository(Defa

        at com.cenqua.fisheye.config.DefaultRepositoryManager$3$

        at com.cenqua.fisheye.config.DefaultRepositoryManager$3$


        at com.cenqua.fisheye.config.DefaultRepositoryManager$

        at com.cenqua.fisheye.config.DefaultRepositoryManager$

        at java.util.concurrent.FutureTask$Sync.innerRun(


        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.


        at java.util.concurrent.ThreadPoolExecutor$



Caused by: com.atlassian.utils.process.ProcessNotStartedException: git could not

 be started

        at com.atlassian.utils.process.ExternalProcessImpl.start(ExternalProcess

        at com.atlassian.utils.process.ExternalProcessImpl.execute(ExternalProce


                                                              65,2-9         0%

1 answer

1 accepted

Accepted Answer
0 votes

Hi Rahul,

This stack trace doesn't look like it was generated by FeCru 3.6.3, this particular exception would be thrown by in this version.  Ensure you have FISHEYE_INST and FISHEYE_HOME folders separate, otherwise you may be experiencing problems with conflicting jars after upgrade.

Anyway, this particular problem seems to be related with FishEye struggling to locate git binary.   Please ensure it is available in the system path or you provide exact path to git binary, see for more details.

Ensure also you have supported version of git, as of 3.6 FishEye supported versions listed here:  Consider upgrading FishEye to 3.7, we started supporting newer versions of git in this release.

Kind regards,

Hi Piotr, fisheye server running on linux.Does it require git executable to be set in fisheye???

thanks How can I configure it to the git.exe???

because we dont have .exe in linux so up-to which directory I should configure git executable??

Ensure you have git binary on your system first, by running git --version from command line. If you don't find it install it, depending on your linux distribution using appropiate command. E.g. apt-get install git, yum install git, etc. Once you have it find out where does it live by running which git, it should return full path to git executable, e.g. /usr/local/bin/git. When you have it, follow guide: go to admin / Global Settings / Server, click Edit details under Git Executable and enter the path you learned. Hope that helps,

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

428 views 0 8
Read article

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