Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
heptapod
heptapod
Commits
cc9ec8288fe2
Commit
e26d8e02
authored
Oct 07, 2016
by
Gabriel Mazetto
Committed by
Achilleas Pipinellis
Nov 16, 2016
Browse files
Updated password examples and improved omnibus troubleshooting
parent
db477ad4cc87
Changes
1
Hide whitespace changes
Inline
Side-by-side
doc/administration/high_availability/redis.md
View file @
cc9ec828
...
...
@@ -45,7 +45,7 @@ Redis.
redis['bind'] = '0.0.0.0'
# If you wish to use Redis authentication (recommended)
redis['password'] = '
R
edis
P
assword'
redis['password'] = '
r
edis
-p
assword
-goes-here
'
```
1.
Run
`sudo touch /etc/gitlab/skip-auto-migrations`
to prevent database migrations
...
...
@@ -132,7 +132,7 @@ the master, and `masterauth` in slaves.
redis['port'] = 6379
## Master redis instance
redis['password'] = '
<huge
password
string
here
>
'
redis['password'] = '
redis-
password
-goes-
here'
```
1.
Edit
`/etc/gitlab/gitlab.rb`
of a slave Redis machine (should be one or more machines):
...
...
@@ -146,7 +146,7 @@ the master, and `masterauth` in slaves.
redis['master'] = false
redis['master_ip'] = '10.10.10.10' # IP of master Redis server
redis['master_port'] = 6379 # Port of master Redis server
redis['master_password'] = "
<huge
password
string
here
>
"
redis['master_password'] = "
redis-
password
-goes-
here"
```
1.
Reconfigure the GitLab for the changes to take effect:
`sudo gitlab-ctl reconfigure`
...
...
@@ -203,7 +203,7 @@ The following steps should be performed in the [GitLab application server](gitla
```ruby
redis['master_name'] = "gitlab-redis"
redis['master_password'] = '
<huge
password
string
here
>
'
redis['master_password'] = '
redis-
password
-goes-
here'
gitlab_rails['redis_sentinels'] = [
{'host' => '10.10.10.1', 'port' => 26379},
{'host' => '10.10.10.2', 'port' => 26379},
...
...
@@ -215,6 +215,21 @@ The following steps should be performed in the [GitLab application server](gitla
### Sentinel troubleshooting
#### Omnibus install
If you get an error like:
`Redis::CannotConnectError: No sentinels available.`
,
there may be something wrong with your configuration files or it can be related
to
[
this issue
][
gh-531
]
.
You must make sure you are defining the same value in
`redis['master_name']`
and
`redis['master_pasword']`
as you defined for your sentinel node.
The way the redis connector
`redis-rb`
works with sentinel is a bit
non-intuitive. We try to hide the complexity in omnibus, but it still requires
a few extra configs.
#### Source install
If you get an error like:
`Redis::CannotConnectError: No sentinels available.`
,
there may be something wrong with your configuration files or it can be related
to
[
this issue
][
gh-531
]
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment