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

Restart shutdown redis on previous bind IP when changed #61

Open
dylancwood opened this issue Mar 31, 2015 · 2 comments
Open

Restart shutdown redis on previous bind IP when changed #61

dylancwood opened this issue Mar 31, 2015 · 2 comments

Comments

@dylancwood
Copy link

When changing the bind address of the redis the managed redis instances, ansible hangs on waiting for the service to come back up. I think that this is because the bind address is changed in the config file, then the redis service is restarted using a command based on the new bind address.

Test

Use this awesome repo to create a redis instance bound to 127.0.0.1, then modify the playbook to bind to the machine's actual IP.

Let me know if you would like more info, or can recommend a solution that I can implement.

@DavidWittman
Copy link
Owner

Thanks again @dylancwood; this is certainly an issue that needs solving. I'd be happy to hear your recommendations on this one.

@DavidWittman
Copy link
Owner

As with #115, this will be resolved by sending a SIGTERM instead of using the shutdown command.

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

No branches or pull requests

2 participants