Commit dcfc2491 authored by Nick Thomas's avatar Nick Thomas

Merge branch 'mk-fix-doc-reconfigure-error' into 'master'

Rearrange instructions in the Geo DB replication setup docs to avoid known error

Closes omnibus-gitlab#2797

See merge request gitlab-org/gitlab-ee!3597
parents d15e704e 66232e35
......@@ -213,6 +213,10 @@ will not be able to perform all necessary configuration steps. Refer to
postgresql['max_replication_slots'] = 1
# postgresql['max_wal_senders'] = 10
# postgresql['wal_keep_segments'] = 10
# Disable automatic database migrations for now
# (until PostgreSQL is restarted and listening on the interface address)
gitlab_rails['auto_migrate'] = false
```
For external PostgreSQL instances, [see additional instructions][external postgresql].
......@@ -228,27 +232,30 @@ will not be able to perform all necessary configuration steps. Refer to
Replication documentation](https://www.postgresql.org/docs/9.6/static/runtime-config-replication.html)
for more information.
1. Save the file and [reconfigure GitLab][] for the database listen changes to
take effect.
**This step will fail.** This is caused by
[Omnibus#2797](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2797).
1. Save the file and [reconfigure GitLab][] for the database listen changes and
the replication slot changes to be applied.
Restart PostgreSQL:
Restart PostgreSQL for its changes to take effect:
```bash
gitlab-ctl restart postgresql
```
[Reconfigure GitLab][reconfigure GitLab] again. It should complete cleanly.
1. Reenable migrations
Edit `/etc/gitlab/gitlab.rb` and **delete** the following lines:
```ruby
# Disable automatic database migrations for now
# (until PostgreSQL is restarted and listening on the interface address)
gitlab_rails['auto_migrate'] = false
```
1. Restart your primary PostgreSQL server to ensure the replication slot
changes take effect (`sudo gitlab-ctl restart postgresql` for
Omnibus-provided PostgreSQL).
Save the file and [reconfigure GitLab][].
1. Now that the PostgreSQL server is set up to accept remote connections, run
`netstat -plnt` to make sure that PostgreSQL is listening on port `5432` to
the server's public IP.
the server's interface address.
1. Verify that clock synchronization is enabled.
......
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