We use a little wrapper to get actual ip address of the machine and confgure redis to listen on loopback interface and eth interface. Cookbook redisio, version 4.2.0.
After initial start, service listens correctly on both interfaces, but after OS (tested on CentOS7, CentOS8, Oracle Linux 8) restart, it listens only on loopback.
Manual restart of the service, fixes the problem.
I started to testing the systemd unit entry and found that simple change from:
We use a little wrapper to get actual ip address of the machine and confgure redis to listen on loopback interface and eth interface. Cookbook redisio, version 4.2.0. After initial start, service listens correctly on both interfaces, but after OS (tested on CentOS7, CentOS8, Oracle Linux 8) restart, it listens only on loopback. Manual restart of the service, fixes the problem.
I started to testing the systemd unit entry and found that simple change from:
to:
in templates/default/redis@.service.erb solves the problem.
redis cookbook version: 4.2.0 chef-client version: 14.15.6
Steps To Reproduce
Create redis service, restart server
:police_car: Expected behavior
Redis service listens on all defined and available interfaces