ansible-redis icon indicating copy to clipboard operation
ansible-redis copied to clipboard

sentinel_26379 Start issue

Open ranjeetranjan opened this issue 7 years ago • 6 comments

fatal: [172.104.5.7]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to start service sentinel_26379: Job for sentinel_26379.service failed because the control process exited with error code. See "systemctl status sentinel_26379.service" and "journalctl -xe" for details.\n"}

root@redis-sentinel ~]# systemctl status sentinel_26379.service ● sentinel_26379.service - Advanced key-value store Loaded: loaded (/etc/systemd/system/sentinel_26379.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Tue 2017-05-16 02:55:45 IST; 37s ago Docs: http://redis.io/documentation, man:redis-sentinel(1) Process: 8194 ExecStart=/opt/redis/bin/redis-server /etc/redis/sentinel_26379.conf --sentinel (code=exited, status=1/FAILURE)

May 16 02:55:45 redis-sentinel systemd[1]: sentinel_26379.service: control process exited, code=exited status=1 May 16 02:55:45 redis-sentinel systemd[1]: Failed to start Advanced key-value store. May 16 02:55:45 redis-sentinel systemd[1]: Unit sentinel_26379.service entered failed state. May 16 02:55:45 redis-sentinel systemd[1]: sentinel_26379.service failed. May 16 02:55:45 redis-sentinel systemd[1]: sentinel_26379.service holdoff time over, scheduling restart. May 16 02:55:45 redis-sentinel systemd[1]: start request repeated too quickly for sentinel_26379.service May 16 02:55:45 redis-sentinel systemd[1]: Failed to start Advanced key-value store. May 16 02:55:45 redis-sentinel systemd[1]: Unit sentinel_26379.service entered failed state. May 16 02:55:45 redis-sentinel systemd[1]: sentinel_26379.service failed.

ranjeetranjan avatar May 15 '17 21:05 ranjeetranjan

@ranjeetranjan Could you please include the playbook which you used and the target distribution (Ubuntu, RedHat, etc.)?

DavidWittman avatar May 15 '17 22:05 DavidWittman

Its Centos -7

Here is my playbook.

  • name: configure the master redis server hosts: redis-master roles:

    • DavidWittman.redis
  • name: configure redis slaves hosts: redis-slave vars:

    • redis_slaveof: 272.14.43.44 6379 roles:
    • DavidWittman.redis
  • name: configure redis sentinel nodes hosts: redis-sentinel vars:

    • redis_sentinel_monitors:
      • name: master01 host: redis-master port: 6379 roles:
    • DavidWittman.redis

Also please see my host file

[redis-master] 272.14.43.44

[redis-slave] 272.14.43.45

[redis-sentinel] 272.14.43.46 redis_sentinel=True

ranjeetranjan avatar May 16 '17 04:05 ranjeetranjan

@DavidWittman , Any suggestion for me?

ranjeetranjan avatar May 18 '17 20:05 ranjeetranjan

@DavidWittman I got the same Issue here. With the exact same errors. OS is Ubuntu 16.04 Ansible is on 2.3.0.0

PhillipAmend avatar May 30 '17 12:05 PhillipAmend

@DavidWittman I have had the same issue as @PhillipAmend with Ubuntu 16.04. Is there a work around or fix for this issue?

Spholt avatar Apr 17 '18 12:04 Spholt

At first sight, I would say that the value of host in redis_sentinel_monitors is wrong, it should be the IP (or fqdn) of the master redis server. In @ranjeetranjan's given configuration it's set to the ansible group name redis-master, which does not resolve to the actual master server.

But it should not fail to start..

bew avatar Jun 11 '19 13:06 bew