JIRA SELF-MANAGED
Also relates to the following exception errors:
GitLabPropertiesNotInitializedExceptionGitHubPropertiesNotInitializedExceptionGerritPropertiesNotInitializedException
Problem
An error is encountered with the next exception ( GitLabPropertiesNotInitializedException ) and you are using NFS.
Example Error log
/rest/gitplugin/1.0/repository/12300/pullRequest [c.b.j.g.rest.exceptionmappers.LoggerHolder] REST API has thrown exception.
com.bigbrassband.jira.git.exceptions.operations.GitLabPropertiesNotInitializedException: Initialization
at com.bigbrassband.jira.git.services.integration.gitlab.GitLabApiService$GitLabRepoApi.getExternalRepoProps(GitLabApiService.java:107)
at com.bigbrassband.jira.git.services.integration.gitlab.GitLabApiService$GitLabRepoApi.getRepoExternalIdForMergeRequests(GitLabApiService.java:113)
at com.bigbrassband.jira.git.services.integration.gitlab.GitLabApiService$GitLabRepoApi.createMergeRequest(GitLabApiService.java:68)
at com.bigbrassband.jira.git.rest.repository.RepositoryResource.createPullRequest(RepositoryResource.java:832)
at com.bigbrassband.jira.git.rest.repository.RepositoryResource.restCreatePullRequest(RepositoryResource.java:796)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
Diagnosis
Check the root of the reason by turning on DEBUG logging for the package – com.bigbrassband.jira.git.services.integration.
The root reason of the exception error can be one of the following:
-
not a valid json entry in
repo.auto.json -
incapability to lock file (
java.io.IOException: No locks available)
Solution 1
Make sure that repo.auto.json (jira/data/git-plugin/###-somerepo/repo.auto.json) contains a valid json.
Solution 2
The lock daemon (lockd) may not be running on the NFS server. Check whether your NFS server supports locking. Update the NFS version, if required.
NFSv4 supporting locking by default was released in 2000. So, it’s a rare case to encounter an NFS server which is not able to lock the /jira/data/git-plugin/###-somerepo/repo.auto.json file these days.
If you still have a question – reach out to our Support Desk or email us at [email protected].
More articles about troubleshooting, workarounds and solutions
Why I am getting the error, “git-upload-pack not permitted”?
Cannot auto-deploy some tracked repositories: Specified origin is incorrect or not supported
Connection Reset when Accessing the Database
“Dangerous use of multiple connections” error on local database
Duplicate entry 0 for key PRIMARY exceptions in log
Error while reindexing – Java heap space / Object too large, rejecting the pack
Error creating git branches and also using NFS (this page)
Fix performance issues for nested cloned repositories with enabled Git Service Permissions mode
Fixing reindex issues using Indexing Queue Viewer
Gitolite integration: Why the Git integration app not see the master branch?
Health Check: Database Collation
Indexing error – Too many open files
Installation fails when installing manually
Jira index error: IndexNotFoundException: no segments* file found
Malformed input or input contains unmappable characters
Personal access token failing Azure DevOps integration with Not Authorized error
Problems with shared home on Azure Storage
Pull request index error: org.json.JSONException
Repositories missing from Azure DevOps integration
“Service proxy has been destroyed” exceptions in log
SQLException ‘Incorrect string value’ in merge requests
SSH key file format is invalid
TFS – Not authorized exception when Jira works thru proxy
Unexpected exception parsing XML document from URL error in log
