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
Happens on systemd-based systems when a lot of integrations are being added by the cookbook. The datadog_monitor resource restarts the agent after each integration file is added, which can make the service hit the maximum number of restarts allowed by systemd by default (5 every 10 seconds). That limit also applies to "manual" restarts of the service.
We get the following error in systemd's journal:
datadog-agent.service: Start request repeated too quickly.
systemd[1]: Failed to start "Datadog Agent".
Root cause: the service resource in datadog_monitor is different from the one in the main chef run (chef limitation, custom resources have their own resource collection), so the restarts that happen there are done immediately instead of being queued up nicely at the end of the run.
The Right Fix would be to remove the service definition from datadog_monitor and make all invocations of datadog_monitor notify a restart on the global service resource, see #323
The text was updated successfully, but these errors were encountered:
Happens on systemd-based systems when a lot of integrations are being added by the cookbook. The
datadog_monitor
resource restarts the agent after each integration file is added, which can make the service hit the maximum number of restarts allowed by systemd by default (5 every 10 seconds). That limit also applies to "manual" restarts of the service.We get the following error in systemd's journal:
Root cause: the service resource in
datadog_monitor
is different from the one in the main chef run (chef limitation, custom resources have their own resource collection), so the restarts that happen there are done immediately instead of being queued up nicely at the end of the run.The Right Fix would be to remove the service definition from
datadog_monitor
and make all invocations ofdatadog_monitor
notify a restart on the global service resource, see #323The text was updated successfully, but these errors were encountered: