kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/administration/repo_checks.md
Jacob Vosmaer e3558ed67e Document how to disable repo checks
2016-04-06 12:26:29 +02:00

1.9 KiB
Raw Blame History

Repo checks

Note: This feature was introduced in GitLab 8.7

Git has a built-in mechanism git fsck to verify the integrity of all data commited to a repository. GitLab administrators can trigger such a check for a project via the admin panel. The checks run asynchronously so it may take a few minutes before the check result is visible on the project admin page. If the checks failed you can see their output on the admin log page under 'repocheck.log'.

Periodical checks

GitLab periodically runs a repo check on all project repositories and wiki repositories in order to detect data corruption problems. A project will be checked no more than once per week. If any projects fail their repo checks all GitLab administrators will receive an email notification of the situation. This notification is sent out no more than once a day.

Disabling periodic checks

You can disable the periodic checks by giving them an empty cron schedule in gitlab.yml.

# For omnibus installations, in /etc/gitlab/gitlab.rb:
gitlab_rails['cron_jobs_repo_check_worker_cron'] = ''

# For installations from source, in config/gitlab.yml:
  cron_jobs:
    repo_check_worker:
      cron: ""

What to do if a check failed

If the repo check fails for some repository you should look up the error in repocheck.log (in the admin panel or on disk; see /var/log/gitlab/gitlab-rails for Omnibus installations or /home/git/gitlab/log for installations from source). Once you have resolved the issue use the admin panel to trigger a new repo check on the project. This will clear the 'check failed' state.

If for some reason the periodical repo check caused a lot of false alarms you can choose to clear ALL repo check states from the admin project index page.