Failed integrations [process,network,disk,post] with new DD agent version

[turnopil]

Hi! I just updated my puppet manifests on Amazon instance with amzn1(centos 6) AMI
Notice: /Stage[main]/Datadog_agent::Redhat::Agent6/Package[datadog-agent]/ensure: ensure changed '1:6.11.2-1' to '1:6.12.1-1'

Info: /etc/datadog-agent/conf.d: Scheduling refresh of Service[datadog-agent]
Notice: /Stage[main]/Datadog_agent/File[/etc/datadog-agent/datadog.yaml]/content:
--- /etc/datadog-agent/datadog.yaml 2019-05-29 04:34:26.532127973 -0500
+++ /tmp/puppet-file20190701-23821-10saejd 2019-07-01 07:32:57.410647850 -0500
@@ -25,6 +25,7 @@

• Cluster:<>
• Environment:<>
• Name:<>
  +additional_checksd: ''
  apm_config:
  enabled: false
  env: none

Info: Computing checksum on file /etc/datadog-agent/datadog.yaml

And got a lot of similar errors for [process,network,disk,post] integrations:

2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/datadog_agent.go:108 in LogMessage) | (ddyaml.py:83) | Unsafe loading of YAML has been disabled - using safe loader instead
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/datadog_agent.go:108 in LogMessage) | (ddyaml.py:83) | Unsafe loading of YAML has been disabled - using safe loader instead
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/check.go:194 in Configure) | could not get a 'postgres' check instance with the new api: init() takes at least 4 arguments (4 given)
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/check.go:195 in Configure) | trying to instantiate the check with the old api, passing agentConfig to the constructor
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/datadog_agent.go:108 in LogMessage) | (ddyaml.py:83) | Unsafe loading of YAML has been disabled - using safe loader instead
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/datadog_agent.go:108 in LogMessage) | (ddyaml.py:83) | Unsafe loading of YAML has been disabled - using safe loader instead
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/datadog_agent.go:108 in LogMessage) | (ddyaml.py:83) | Unsafe loading of YAML has been disabled - using safe loader instead
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/check.go:210 in Configure) | passing agentConfig to the constructor is deprecated, please use the get_config function from the 'datadog_agent' package (postgres).
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/datadog_agent.go:108 in LogMessage) | (ddyaml.py:83) | Unsafe loading of YAML has been disabled - using safe loader instead
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/datadog_agent.go:108 in LogMessage) | (ddyaml.py:83) | Unsafe loading of YAML has been disabled - using safe loader instead
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/check.go:194 in Configure) | could not get a 'process' check instance with the new api: init() takes at least 4 arguments (4 given)
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/check.go:195 in Configure) | trying to instantiate the check with the old api, passing agentConfig to the constructor
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/datadog_agent.go:108 in LogMessage) | (ddyaml.py:83) | Unsafe loading of YAML has been disabled - using safe loader instead
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/datadog_agent.go:108 in LogMessage) | (ddyaml.py:83) | Unsafe loading of YAML has been disabled - using safe loader instead
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/datadog_agent.go:108 in LogMessage) | (ddyaml.py:83) | Unsafe loading of YAML has been disabled - using safe loader instead
2019-07-01 08:26:05 CDT | CORE | WARN | (pkg/collector/python/check.go:210 in Configure) | passing agentConfig to the constructor is deprecated, please use the get_config function from the 'datadog_agent' package (process).

And I cat find a way how to fix this issue

[amontalban]

@turnopil I'm having the same problem. Did you manage to fix this? Thanks!

[albertvaka]

The issue with additional_checksd was fixed in version 2.7.0. Which version are you using? Also, the warnings you see can safely be ignored.