| ... | @@ -46,7 +46,7 @@ sudo gitlab-rake gitlab:geo:check |
... | @@ -46,7 +46,7 @@ sudo gitlab-rake gitlab:geo:check |
|
|
|
|
|
|
|
Example output:
|
|
Example output:
|
|
|
|
|
|
|
|
```text
|
|
```plaintext
|
|
|
Checking Geo ...
|
|
Checking Geo ...
|
|
|
|
|
|
|
|
GitLab Geo is available ... yes
|
|
GitLab Geo is available ... yes
|
| ... | @@ -79,7 +79,7 @@ sudo gitlab-rake geo:status |
... | @@ -79,7 +79,7 @@ sudo gitlab-rake geo:status |
|
|
|
|
|
|
|
Example output:
|
|
Example output:
|
|
|
|
|
|
|
|
```text
|
|
```plaintext
|
|
|
http://secondary.example.com/
|
|
http://secondary.example.com/
|
|
|
-----------------------------------------------------
|
|
-----------------------------------------------------
|
|
|
GitLab Version: 11.10.4-ee
|
|
GitLab Version: 11.10.4-ee
|
| ... | @@ -134,11 +134,11 @@ sudo gitlab-rake gitlab:geo:check |
... | @@ -134,11 +134,11 @@ sudo gitlab-rake gitlab:geo:check |
|
|
It displays the current machine's node name and whether the matching database
|
|
It displays the current machine's node name and whether the matching database
|
|
|
record is a **primary** or **secondary** node.
|
|
record is a **primary** or **secondary** node.
|
|
|
|
|
|
|
|
```
|
|
```plaintext
|
|
|
This machine's Geo node name matches a database record ... yes, found a secondary node named "Shanghai"
|
|
This machine's Geo node name matches a database record ... yes, found a secondary node named "Shanghai"
|
|
|
```
|
|
```
|
|
|
|
|
|
|
|
```
|
|
```plaintext
|
|
|
This machine's Geo node name matches a database record ... no
|
|
This machine's Geo node name matches a database record ... no
|
|
|
Try fixing it:
|
|
Try fixing it:
|
|
|
You could add or update a Geo node database record, setting the name to "https://example.com/".
|
|
You could add or update a Geo node database record, setting the name to "https://example.com/".
|
| ... | @@ -157,7 +157,7 @@ sudo gitlab-rake gitlab:geo:check |
... | @@ -157,7 +157,7 @@ sudo gitlab-rake gitlab:geo:check |
|
|
|
|
|
|
|
1. Rails did not provide a password when connecting to the database
|
|
1. Rails did not provide a password when connecting to the database
|
|
|
|
|
|
|
|
```text
|
|
```plaintext
|
|
|
Checking Geo ...
|
|
Checking Geo ...
|
|
|
|
|
|
|
|
GitLab Geo is available ... Exception: fe_sendauth: no password supplied
|
|
GitLab Geo is available ... Exception: fe_sendauth: no password supplied
|
| ... | @@ -170,7 +170,7 @@ sudo gitlab-rake gitlab:geo:check |
... | @@ -170,7 +170,7 @@ sudo gitlab-rake gitlab:geo:check |
|
|
|
|
|
|
|
1. Rails is unable to connect to the database
|
|
1. Rails is unable to connect to the database
|
|
|
|
|
|
|
|
```text
|
|
```plaintext
|
|
|
Checking Geo ...
|
|
Checking Geo ...
|
|
|
|
|
|
|
|
GitLab Geo is available ... Exception: FATAL: no pg_hba.conf entry for host "1.1.1.1", user "gitlab", database "gitlabhq_production", SSL on
|
|
GitLab Geo is available ... Exception: FATAL: no pg_hba.conf entry for host "1.1.1.1", user "gitlab", database "gitlabhq_production", SSL on
|
| ... | @@ -186,7 +186,7 @@ sudo gitlab-rake gitlab:geo:check |
... | @@ -186,7 +186,7 @@ sudo gitlab-rake gitlab:geo:check |
|
|
|
|
|
|
|
1. Rails has supplied the incorrect password
|
|
1. Rails has supplied the incorrect password
|
|
|
|
|
|
|
|
```text
|
|
```plaintext
|
|
|
Checking Geo ...
|
|
Checking Geo ...
|
|
|
GitLab Geo is available ... Exception: FATAL: password authentication failed for user "gitlab"
|
|
GitLab Geo is available ... Exception: FATAL: password authentication failed for user "gitlab"
|
|
|
FATAL: password authentication failed for user "gitlab"
|
|
FATAL: password authentication failed for user "gitlab"
|
| ... | @@ -200,7 +200,7 @@ sudo gitlab-rake gitlab:geo:check |
... | @@ -200,7 +200,7 @@ sudo gitlab-rake gitlab:geo:check |
|
|
|
|
|
|
|
1. Check returns not a secondary node
|
|
1. Check returns not a secondary node
|
|
|
|
|
|
|
|
```text
|
|
```plaintext
|
|
|
Checking Geo ...
|
|
Checking Geo ...
|
|
|
|
|
|
|
|
GitLab Geo is available ... yes
|
|
GitLab Geo is available ... yes
|
| ... | @@ -217,7 +217,7 @@ sudo gitlab-rake gitlab:geo:check |
... | @@ -217,7 +217,7 @@ sudo gitlab-rake gitlab:geo:check |
|
|
|
|
|
|
|
1. Check returns Exception: PG::UndefinedTable: ERROR: relation "geo_nodes" does not exist
|
|
1. Check returns Exception: PG::UndefinedTable: ERROR: relation "geo_nodes" does not exist
|
|
|
|
|
|
|
|
```text
|
|
```plaintext
|
|
|
Checking Geo ...
|
|
Checking Geo ...
|
|
|
|
|
|
|
|
GitLab Geo is available ... no
|
|
GitLab Geo is available ... no
|
| ... | @@ -483,7 +483,7 @@ when promoting a secondary to a primary node with strategies to resolve them. |
... | @@ -483,7 +483,7 @@ when promoting a secondary to a primary node with strategies to resolve them. |
|
|
When [promoting a **secondary** node](../disaster_recovery/index.md#step-3-promoting-a-secondary-node),
|
|
When [promoting a **secondary** node](../disaster_recovery/index.md#step-3-promoting-a-secondary-node),
|
|
|
you might encounter the following error:
|
|
you might encounter the following error:
|
|
|
|
|
|
|
|
```text
|
|
```plaintext
|
|
|
Running gitlab-rake geo:set_secondary_as_primary...
|
|
Running gitlab-rake geo:set_secondary_as_primary...
|
|
|
|
|
|
|
|
rake aborted!
|
|
rake aborted!
|
| ... | @@ -523,7 +523,7 @@ This section documents ways to fix potential Foreign Data Wrapper errors. |
... | @@ -523,7 +523,7 @@ This section documents ways to fix potential Foreign Data Wrapper errors. |
|
|
When setting up Geo, you might see this warning in the `gitlab-rake
|
|
When setting up Geo, you might see this warning in the `gitlab-rake
|
|
|
gitlab:geo:check` output:
|
|
gitlab:geo:check` output:
|
|
|
|
|
|
|
|
```text
|
|
```plaintext
|
|
|
GitLab Geo tracking database Foreign Data Wrapper schema is up-to-date? ... foreign data wrapper is not configured
|
|
GitLab Geo tracking database Foreign Data Wrapper schema is up-to-date? ... foreign data wrapper is not configured
|
|
|
```
|
|
```
|
|
|
|
|
|
| ... | @@ -607,7 +607,7 @@ To check the configuration: |
... | @@ -607,7 +607,7 @@ To check the configuration: |
|
|
1. Check that the foreign server mapping is correct via `\des+`. The
|
|
1. Check that the foreign server mapping is correct via `\des+`. The
|
|
|
results should look something like this:
|
|
results should look something like this:
|
|
|
|
|
|
|
|
```
|
|
```plaintext
|
|
|
gitlabhq_geo_production=# \des+
|
|
gitlabhq_geo_production=# \des+
|
|
|
List of foreign servers
|
|
List of foreign servers
|
|
|
-[ RECORD 1 ]--------+------------------------------------------------------------
|
|
-[ RECORD 1 ]--------+------------------------------------------------------------
|
| ... | @@ -643,7 +643,7 @@ To check the configuration: |
... | @@ -643,7 +643,7 @@ To check the configuration: |
|
|
|
|
|
|
|
1. Check that the user mapping is configured properly via `\deu+`:
|
|
1. Check that the user mapping is configured properly via `\deu+`:
|
|
|
|
|
|
|
|
```
|
|
```plaintext
|
|
|
gitlabhq_geo_production=# \deu+
|
|
gitlabhq_geo_production=# \deu+
|
|
|
List of user mappings
|
|
List of user mappings
|
|
|
Server | User name | FDW Options
|
|
Server | User name | FDW Options
|
| ... | @@ -731,7 +731,7 @@ GitLab can error with a `Geo database has an outdated FDW remote schema` message |
... | @@ -731,7 +731,7 @@ GitLab can error with a `Geo database has an outdated FDW remote schema` message |
|
|
|
|
|
|
|
For example:
|
|
For example:
|
|
|
|
|
|
|
|
```text
|
|
```plaintext
|
|
|
Geo database has an outdated FDW remote schema. It contains 229 of 236 expected tables. Please refer to Geo Troubleshooting.
|
|
Geo database has an outdated FDW remote schema. It contains 229 of 236 expected tables. Please refer to Geo Troubleshooting.
|
|
|
```
|
|
```
|
|
|
|
|
|
| ... | |
... | |
| ... | | ... | |