geerlingguy / ansible-role-redis

Ansible Role - Redis
https://galaxy.ansible.com/geerlingguy/redis/
MIT License
254 stars 197 forks source link

Fix #39: Redis won't start with ipv6 disabled #51

Closed agrrh closed 3 years ago

agrrh commented 4 years ago

Fixes #39 by putting config in place before installing a package

agrrh commented 4 years ago

Should be fixed now %)

Upd: Oh, come on!

stale[bot] commented 4 years ago

This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark pull requests as stale.

agrrh commented 4 years ago

@geerlingguy Could you take a look at this, please?

stale[bot] commented 4 years ago

This issue is no longer marked for closure.

joelpittet commented 3 years ago

@agrrh I'm running into this but got it to work by just changing one line using whatever Ubuntu comes with vagrant_box: geerlingguy/drupal-vm I think 18.04

I'm trying out your patch to see if it works as a solution but wondering if your OS also needs this? sed -i 's/^supervised no/supervised systemd/' /etc/redis/redis.conf https://github.com/geerlingguy/drupal-vm/issues/2107

notasysadmin

joelpittet commented 3 years ago

No dice, I destroyed and built with this patch applied and didn't get any better results.

joelpittet commented 3 years ago

I'm experimenting with this patch + supervised auto but wondering why the permission changes @agrrh ?

joelpittet commented 3 years ago

No luck still running into this timeout, I even stopped configuring and letting the package just install with defaults.

agrrh commented 3 years ago

Hey there, @joelpittet !

My case was all around IPv6 disabled and Redis tried to bind to ::1

supervised parameter configures how Redis handles various signals and ENV variables, so it wasn't the thing.

Permission changes are related to difference in Ubuntu/CentOS permissions for /etc contents, I guess. Sadly, there's a confusing message in commit and right now I can't remember particular cause.

joelpittet commented 3 years ago

No luck still running into this timeout after install status check, I even stopped "configuring" and letting the package just install with defaults /etc/redis/redis.conf.

@agrrh Thanks for letting me know the details, I can see how this patch could help you and I'm +1 to committing it.