diff options
author | Jacob Vosmaer <contact@jacobvosmaer.nl> | 2016-04-06 13:47:05 +0200 |
---|---|---|
committer | Jacob Vosmaer <contact@jacobvosmaer.nl> | 2016-04-06 13:47:05 +0200 |
commit | 5cf56e56470e695b10db02dff70d0f0b50060518 (patch) | |
tree | d46ecd17857f8e49abda15c03576c099e2bf39df /doc/administration | |
parent | e3558ed67e7e829fe5148c3fb2fe80ed045fe1b4 (diff) | |
download | gitlab-ce-5cf56e56470e695b10db02dff70d0f0b50060518.tar.gz |
Rename almost all the things
Diffstat (limited to 'doc/administration')
-rw-r--r-- | doc/administration/repository_checks.md (renamed from doc/administration/repo_checks.md) | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/administration/repo_checks.md b/doc/administration/repository_checks.md index 81087f3ac1c..77f28209f2f 100644 --- a/doc/administration/repo_checks.md +++ b/doc/administration/repository_checks.md @@ -1,4 +1,4 @@ -# Repo checks +# Repository checks _**Note:** This feature was [introduced][ce-3232] in GitLab 8.7_ @@ -13,10 +13,10 @@ output on the admin log page under 'repocheck.log'. ## Periodical checks -GitLab periodically runs a repo check on all project repositories and +GitLab periodically runs a repository 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 +fail their repository checks all GitLab administrators will receive an email notification of the situation. This notification is sent out no more than once a day. @@ -27,27 +27,27 @@ schedule in gitlab.yml. ``` # For omnibus installations, in /etc/gitlab/gitlab.rb: -gitlab_rails['cron_jobs_repo_check_worker_cron'] = '' +gitlab_rails['cron_jobs_repository_check_worker_cron'] = '' ``` ``` # For installations from source, in config/gitlab.yml: cron_jobs: - repo_check_worker: + repository_check_worker: cron: "" ``` ## What to do if a check failed -If the repo check fails for some repository you shouldlook up the error +If the repository check fails for some repository you shouldlook 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 +resolved the issue use the admin panel to trigger a new repository 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 +If for some reason the periodical repository check caused a lot of false +alarms you can choose to clear ALL repository check states from the admin project index page. --- |