Commit b5d169cc authored by Michael Kozono's avatar Michael Kozono Committed by Evan Read

Geo docs: Add troubleshooting help for gitlab-pg-ctl

parent a11dfc16
...@@ -139,6 +139,8 @@ do this manually. ...@@ -139,6 +139,8 @@ do this manually.
sudo gitlab-pg-ctl promote sudo gitlab-pg-ctl promote
``` ```
In GitLab 12.8 and earlier, see [Message: "sudo: gitlab-pg-ctl: command not found"](../replication/troubleshooting.md#message-sudo-gitlab-pg-ctl-command-not-found).
1. Edit `/etc/gitlab/gitlab.rb` on every machine in the **secondary** to 1. Edit `/etc/gitlab/gitlab.rb` on every machine in the **secondary** to
reflect its new status as **primary** by removing any lines that enabled the reflect its new status as **primary** by removing any lines that enabled the
`geo_secondary_role`: `geo_secondary_role`:
......
...@@ -514,6 +514,27 @@ or `gitlab-ctl promote-to-primary-node`, either: ...@@ -514,6 +514,27 @@ or `gitlab-ctl promote-to-primary-node`, either:
bug](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/22021) was bug](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/22021) was
fixed. fixed.
### Message: "sudo: gitlab-pg-ctl: command not found"
When
[promoting a **secondary** node with HA](../disaster_recovery/index.md#promoting-a-secondary-node-with-ha),
you need to run the `gitlab-pg-ctl` command to promote the PostgreSQL
read-replica database.
In GitLab 12.8 and earlier, this command will fail with the message:
```plaintext
sudo: gitlab-pg-ctl: command not found
```
In this case, the workaround is to use the full path to the binary, for example:
```shell
sudo /opt/gitlab/embedded/bin/gitlab-pg-ctl promote
```
GitLab 12.9 and later are [unaffected by this error](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/5147).
## Fixing Foreign Data Wrapper errors ## Fixing Foreign Data Wrapper errors
This section documents ways to fix potential Foreign Data Wrapper errors. This section documents ways to fix potential Foreign Data Wrapper errors.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment