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_26379 Start issue #166

Open
ranjeetranjan opened this issue May 15, 2017 · 6 comments
Open

sentinel_26379 Start issue #166

ranjeetranjan opened this issue May 15, 2017 · 6 comments

Comments

@ranjeetranjan
Copy link

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.

@DavidWittman
Copy link
Owner

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

@ranjeetranjan
Copy link
Author

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
Copy link
Author

ranjeetranjan commented May 18, 2017

@DavidWittman ,
Any suggestion for me?

@PhillipAmend
Copy link

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

@Spholt
Copy link

Spholt commented Apr 17, 2018

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

@bew
Copy link
Contributor

bew commented Jun 11, 2019

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..

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

5 participants