Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Ansible: "Redis started at boot" step, fails due to: Systemd fatal error /etc/redis/6379.conf not found #265

Open
825i opened this issue May 10, 2021 · 0 comments

Comments

@825i
Copy link

825i commented May 10, 2021

I am getting via journalctl -xfeu redis_6379:

May 10 11:22:12 linux redis-server[34057]: 34057:C 10 May 2021 11:22:12.368 # Fatal error, can't open config file '/etc/redis/6379.conf': No such file or directory
May 10 11:22:12 linux systemd[1]: redis_6379.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- An ExecStart= process belonging to unit redis_6379.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.

It looks like the script is trying to start the service via systemd, but systemd is looking for the redis.conf file which was specified in the systemd template, but this has not been created yet due to redis having never been run yet. This is a bit of a catch 22.

So it would seem that a config file must be created before this step in the play can be run.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant