Fisheye Can't Start GIT Repository Due to Non-Zero Exit Code
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
You are getting the following error message when trying to start a Git repository:
1
2
3
4
5
6
7
8
9
ERROR - Problem processing revisions from repo Git due to class com.atlassian.fisheye.plugins.scm.utils.process.ProcessException - Non-zero exit code: 138
com.atlassian.fisheye.plugins.scm.utils.process.ProcessException: Non-zero exit code: 138
at com.atlassian.fisheye.plugins.scm.utils.process.PluggableProcessHandler.complete(PluggableProcessHandler.java:66)
at com.atlassian.fisheye.plugins.scm.utils.process.ExternalProcess.finish(ExternalProcess.java:204)
at com.atlassian.fisheye.plugins.scm.utils.process.ExternalProcess.execute(ExternalProcess.java:218)
at com.atlassian.fisheye.git.client.GitContext.executeCommand(GitContext.java:138)
at com.atlassian.fisheye.git.client.GitContext.executeCommand(GitContext.java:96)
at com.atlassian.fisheye.git.client.GitContext.executeCommand(GitContext.java:90)
at com.atlassian.fisheye.git.client.GitContext.executeCommand(GitContext.java:86)
Cause #1
This can be caused by an incorrect repository path setting. For instance:
1
<git location="file:///Users/amyers/git/test.git" path="/"/>
If you include the leading / for the path, it will be interpreted as an absolute path on the file system when Fisheye tries to run git.
Cause #2
Certain versions of the git client can experience segmentation fault when character encoding in committers' name is not UTF-8, however this may not exclusively be the cause. Such behavior was noticed using git versions 1.8.2.1 and 1.8.1.5, but likely other versions may be affected.
Resolution for cause #1
Ensure that you have configured the GIT repository correctly, going by the example above the solution would be to remove the leading / from the repository configuration.
1
<git location="file:///Users/amyers/git/test.git" path=""/>Resolution for cause #2
Upgrade your git client to a newer version, see Supported platforms for reference.
Was this helpful?