Skip to content
Snippets Groups Projects
Commit d1adc5d613c9 authored by Alexandr Tanayno's avatar Alexandr Tanayno
Browse files

Add section about stuck reconfigure during re-installation

parent 754e15c9cfb0
2 merge requests!109heptapod#1351: making Heptapod 0.41 the new oldstable,!105heptapod#1283: making 0.41 the new stable
......@@ -115,6 +115,7 @@
sudo systemctl disable gitlab-runsvdir
sudo rm /usr/lib/systemd/system/gitlab-runsvdir.service
sudo systemctl daemon-reload
sudo systemctl reset-failed
sudo gitlab-ctl uninstall
```
......
......@@ -820,6 +820,17 @@
Refer to [issue 341573](https://gitlab.com/gitlab-org/gitlab/-/issues/341573) for more details.
## Reconfigure is stuck when re-installing GitLab
Because of a [known issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7776), you can see the reconfigure process stuck at
`ruby_block[wait for logrotate service socket] action run` after uninstalling GitLab and trying to install it again. This problem occurs when one of the `systemctl` commands are
not executed when [uninstalling GitLab](installation/index.md#uninstall-the-linux-package-omnibus).
To resolve this issue:
- Make sure you followed all the steps when uninstalling GitLab and perform them if necessary.
- Follow the workaround in [issue 7776](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7776).
## Mirroring the GitLab `yum` repository with Pulp or Red Hat Satellite fails
Direct mirroring of the Omnibus GitLab `yum` repositories located at <https://packages.gitlab.com/gitlab/> with [Pulp](https://pulpproject.org/) or
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment