Repository Troubleshooting

Here is some guidance for some common issues you may encounter with your repository.

Failed Commits

• If you see that commits are failing, try reboot AIQ.

• If the repository still displays WORKING status but not is committing, kill all java processes, drop the DB and recreate the DB, and restart AIQ.

File Manager Stuck

If the File Manager is stuck / loading forever or stuck may indicate that the S3 repository configured to a wrong AWS region. Remember that if you are running AIQ from an S3 instance, in order for AIQ to connect to repository and function as expected, the S3 repository must be in the same region as the AWS instance.

Delete the repository and create it again with a valid region. Once that is complete, check the File Manager to verify that it is showing the repository files.

Preferences - WORKING Status

When the WORKING status is visible from the Preferences interface, it only indicates that the repository configuration settings were saved correctly. You need to check in other AIQ user interfaces such as Web Deisgner, etc to confirm that the files are visible.

Git Tokens

If your Git repository was working yesterday and today it fails and it still says "WORKING", check to see if the Git token has expired. Delete the current repository and re-clone it using the new token.

Most issues are related to token expiration, or even branch protection, which will require you to make updates ot changes in your environment.

Long File Names

If you have problems with long file names in Git, make sure the following parameter is set.

git config --system core.longpaths true

SSL Issues

If you have problems SSL verification in Git, make sure the following parameter is set.

git config http.sslVerify "false"

GIT Failing to Authenticate with SSH

Below are some of the methods that can be tried when working with Git and SSH.

• Make sure that the .ssh/known_host file does have the correct entry for the Git domain.

• For some of the cases simple ssh <TFS git url> would be enough to add a proper entry to the known_host file. This is for TFS Git Repo.

• In the case of cloning a GitLab repo with SSH above might not be enough. It will be required to manually add the following lines into the .ssh/known_hosts file.

  http://gitlab.com  ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAfuCHKVTjquxvt6CM6tdG4SLp********
  http://gitlab.com  ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAA**********************
  http://gitlab.com  ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNT**************

  Reference: >https://docs.gitlab.com/ee/user/gitlab_com/index.html#ssh-host-keys-fingerprints

• Make sure the private key is in the required format. key pair to be used must be generated in PEM format using the following command: ssh-keygen -t rsa -p pem

  For that the private key begins with

  ------ BEGIN RSA PRIVATE

  If the first line of your private key has "BEGIN OPENSSL" or other strings then you will likely get an invalid private key error while trying to clone.

GIT Failures - Other Considerations

• Have each user check their repositories configurations to make sure they delete the ones not used, and if the fetched branch name is still a branch that does exist in the remote (maybe someone might have deleted a branch that is set up in an AIQ repository configuration).

• If you have deleted users and did not delete their associated git repositories, please recreate the user with the same user name and any password, navigate to Preferences and delete the user-configured repositories. This is automatically taken care of in AIQ and all repository configurations will be deleted as part of the process of removing a user).

• If a repository configuration in using a non-master branch is in "FAILING" status, try changing the branch back to MASTER and then back to the desired branch.

• Check that the AIQ server's main HD has enough available space.

• Check if the failing repository branch has any huge file or folder with a huge number of files in it as some limit.