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

Repeated systemctl restarts cause failure #24

Open
dgivens opened this issue Aug 27, 2015 · 0 comments
Open

Repeated systemctl restarts cause failure #24

dgivens opened this issue Aug 27, 2015 · 0 comments

Comments

@dgivens
Copy link
Contributor

dgivens commented Aug 27, 2015

In testing the cookbook under Debian Jessie, I am getting a failure due to the repeated attempts to restart the agent service too quickly for systemd's liking.

Aug 27 19:20:07 default-debian-81 systemd[1]: rackspace-monitoring-agent.service start request repeated too quickly, refusing to start.
Aug 27 19:20:07 default-debian-81 systemd[1]: Failed to start rackspace-monitoring-agent.service.
Aug 27 19:20:07 default-debian-81 systemd[1]: Unit rackspace-monitoring-agent.service entered failed state.

This is triggered for me when the chef has converged up to recipe[rackspace_monitoring_check_test::load]. I think the way the rackspace_monitoring_check resource is calling the restart for the service, it's not delaying to the end of execution as would seem to be expected. I think the service resource identified within the rackspace_monitoring_check resource is a separate instance of the service for each instance of the resource.

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

1 participant