Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sentinel Bind #102

Closed

Conversation

sjpbeale
Copy link
Contributor

Redis 3.2 introduced 'protected-mode' to enhance security. The feature introduces an error in the sentinels when trying to connect from non loopback interface :

DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients....

Fix adds 'bind' to the sentinel template in order to allow the sentinels to communicate.

class { 'redis::sentinel':
  sentinel_bind => '0.0.0.0',
}

Example tested in production, Centos 6.5, Redis 3.2.1. Configuration, Master / Slave plus multiple Client Sentinels.

@mnaser
Copy link
Contributor

mnaser commented Sep 11, 2016

Welp, just noticed this PR exists, just submitted a similar one #109 with tests.. Be nice if this (or the other) get merged.

@petems petems mentioned this pull request Oct 14, 2016
@petems petems closed this in #120 Oct 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants