-
Notifications
You must be signed in to change notification settings - Fork 572
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
Service is not enabled for autostart at reboot #363
Comments
Can you please give some more information:
|
OS: CentOS 7.3
And this the log of the part of the role Ansible version: 2.4.3 |
Hmmm... I think you're right. This piece of code(ish) should be in the role:
But I can't find it anywhere: I'm slammed this week, but maybe @jlozadad @UnderGreen , or @sebalix can help out. |
Hi, The service currently is getting enabled by the following task calling a handler:
The handler is what is enabling the service in systemd:
Which is working for me when installing PostgreSQL 9.6.
It would might be better to have two tasks one for "systemd" and one for "service" so if any changes are made to the systemd unit file it can call daemon_reload. Regards, Tim |
@tvigers your last comment is what I had submitted originally. I haven't been keeping track of what has changed but, it was there. |
@tvigers Indeed the service is being started but it's not being enabled. Being enabled means that it's auto-started on system boot. The variable |
Just stumbled over this... Can we expect a fix anytime soon or should someone open a PR to help out? |
Hitting this issue right now, the service is never enabled. |
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! |
Hello, Forgive me for my bad english.
I've set the "postgresql_service_enabled: true" but the service is not "enabled" after running the role.
When I try to make a grep, I can't find any tasks using this variable:
Is there a way to autostart the service using the original role ?
Actually I have added this task in configure.yml:
The text was updated successfully, but these errors were encountered: