-
Notifications
You must be signed in to change notification settings - Fork 262
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
datadog cookbook constantly failing on windows servers #536
Comments
Hi @benorgil and sorry for the very late reply. To pin the version of the Agent that's installed by the cookbook, you should make sure Also, please note that, currently, the cookbook will reinstall the Agent if you clear Chef's cache directory. Unfortunately this was done to support older versions of Chef (<12.6), we'll attempt to drop support for these old versions and improve the logic in v3.0 of the present cookbook. Does this info help? Which version of Chef are you running? |
I'm getting the same error code '1603' whenever datadog upgrades the agent. I have datadog pinned to version 6.11.0 in chef, so some of my old clients are upgrading. It removes the agent with no problem but fails to re-install it. I experience the same issue when trying to install the msi manually from the server itself. Browsing on the datadog site for properly uninstalling the agent https://docs.datadoghq.com/agent/faq/how-do-i-uninstall-the-agent/?tab=agentv6 However, the user who previously manually installed an older version of datadog left the company and their account no longer exists. Does this mean I can never install datadog on these servers again? There has to be a better way to handle uninstalls/installs. |
We are running the datadog cookbook through the use of a in-house wrapper to enable log aggregation. The Linux side of the cookbook works fine, however it keeps failing on the Windows installs.
Running handlers: |
Not sure whats causing this, but every few weeks all my windows chef runs start failing because of this datadog cookbook. I have the version pinned to 2.11.0 so it should not be updating the client, but it looks like it does periodically try to reinstall?
This kills me because every time this happens I have to interactively log into each server and run this command for it to force uninstall so the chef run will succeed:
msiexec /qn /i "c:\chef\cache\ddagent-cli.msi" /norestart ALLUSERS=1 /log dd-agent-install-log.txt NOTUPGRADE=1
Is it trying to reinstall the msi? why?
Errors from failed runs:
Recipe: datadog::dd-agent
ruby_block[datadog-api-key-unset] action run[2018-03-30T11:23:25-04:00] INFO: Processing ruby_block[datadog-api-key-
unset] action run (datadog::dd-agent line 21)
(skipped due to only_if)
Recipe: datadog::_install-windows
windows_package[Datadog Agent removal] action nothing[2018-03-30T11:23:25-04:00] INFO: Processing windows_package[Da
tadog Agent removal] action nothing (datadog::_install-windows line 58)
(skipped due to action :nothing)
remote_file[c:/chef/cache/ddagent-cli.msi] action create[2018-03-30T11:23:25-04:00] INFO: Processing remote_file[c:/
chef/cache/ddagent-cli.msi] action create (datadog::_install-windows line 68)
(up to date)
windows_package[Datadog Agent] action install[2018-03-30T11:23:26-04:00] INFO: Processing windows_package[Datadog Ag
ent] action install (datadog::_install-windows line 83)
================================================================================
Error executing action
install
on resource 'windows_package[Datadog Agent]'Mixlib::ShellOut::ShellCommandFailed
Expected process to exit with [0, 3010], but received '1603'
---- Begin output of msiexec /qn /i "c:\chef\cache\ddagent-cli.msi" /norestart ALLUSERS=1 ----
STDOUT:
STDERR:
---- End output of msiexec /qn /i "c:\chef\cache\ddagent-cli.msi" /norestart ALLUSERS=1 ----
Ran msiexec /qn /i "c:\chef\cache\ddagent-cli.msi" /norestart ALLUSERS=1 returned 1603
Resource Declaration:
In c:/chef/cache/cookbooks/datadog/recipes/_install-windows.rb
83: windows_package 'Datadog Agent' do # ~FC009
84: source temp_file
85: installer_type installer_type
86: options install_options
87: action :install
88: if respond_to?(:returns)
89: returns [0, 3010]
90: else
91: success_codes [0, 3010]
92: end
93: end
The text was updated successfully, but these errors were encountered: