You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
This is triggered for me when the chef has converged up to
recipe[rackspace_monitoring_check_test::load]
. I think the way therackspace_monitoring_check
resource is calling therestart
for the service, it's not delaying to the end of execution as would seem to be expected. I think theservice
resource identified within therackspace_monitoring_check
resource is a separate instance of theservice
for each instance of the resource.The text was updated successfully, but these errors were encountered: