aws-samples / aws-samples/amazon-cloudwatch-container-insights
Issue /usr/share/collectd/types.db: no such file or director
- Dominant language
- Shell
- Stars
- 178
- Forks
- 117
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 3
Description
I was using https://github.com/aws-samples/amazon-cloudwatch-container-insights/blob/main/k8s-deployment-manifest-templates/deployment-mode/sidecar/combination/combination.yaml for setting up cloudwatch agent in the sidecar container
I am getting following error
```2023-10-30T12:46:54Z E! [telegraf] Error running agent: Error loading config file /opt/aws/amazon-cloudwatch-agent/etc/amazon-cloudwatch-agent.toml: error parsing socket_listener, open /usr/share/collectd/types.db: no such file or directory```
Contributor guide
Research direction
Start with the referenced k8s-deployment-manifest-templates/deployment-mode/sidecar/combination/combination.yaml and inspect how it configures the CloudWatch Agent. Check the reported /opt/aws/amazon-cloudwatch-agent/etc/amazon-cloudwatch-agent.toml error and its /usr/share/collectd/types.db dependency; done means the sidecar starts without this missing-file error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100