diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-11-05 00:09:59 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-11-05 00:09:59 +0300 |
commit | 8fc2555ccce63aa5641b123c154389cff593e0d7 (patch) | |
tree | 74f0200c2f7b9a5349120599daa762ea36df697a /doc/administration/troubleshooting | |
parent | 821ba7ce78f6508fe03e3f7c9bc0b9542fa86485 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/troubleshooting')
-rw-r--r-- | doc/administration/troubleshooting/postgresql.md | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/doc/administration/troubleshooting/postgresql.md b/doc/administration/troubleshooting/postgresql.md index 24d7de40b2b..e392bdffe30 100644 --- a/doc/administration/troubleshooting/postgresql.md +++ b/doc/administration/troubleshooting/postgresql.md @@ -236,3 +236,26 @@ To temporarily change the statement timeout: 1. Perform the action for which you need a different timeout (for example the backup or the Rails command). 1. Revert the edit in `/var/opt/gitlab/gitlab-rails/etc/database.yml`. + +## Troubleshooting + +### Database is not accepting commands to avoid wraparound data loss + +This error likely means that AUTOVACUUM is failing to complete its run: + +```plaintext +ERROR: database is not accepting commands to avoid wraparound data loss in database "gitlabhq_production" +``` + +To resolve the error, run `VACUUM` manually: + +1. Stop GitLab with the command `gitlab-ctl stop`. +1. Place the database in single-user mode with the command: + + ```shell + /opt/gitlab/embedded/bin/postgres --single -D /var/opt/gitlab/postgresql/data gitlabhq_production + ``` + +1. In the `backend>` prompt, run `VACUUM;`. This command can take several minutes to complete. +1. Wait for the command to complete, then press <kbd>Control</kbd> + <kbd>D</kbd> to exit. +1. Start GitLab with the command `gitlab-ctl start`. |