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
I have tried applying the fix listed in this issue #188 on EKS 1.21 with the containerd runtime enabled. However, I'm still getting the same error messages:
2021-08-21T00:09:00Z W! No pod metric collected, metrics count is still 5 is containerd socket mounted? #188
2021-08-21T00:09:05Z W! [outputs.cloudwatchlogs] Invalid SequenceToken used, will use new token and retry: The given sequenceToken is invalid. The next expected sequenceToken is: 49605661750447750614958043896578931231172344896032866930
2021-08-21T00:09:05Z W! [outputs.cloudwatchlogs] Retried 0 time, going to sleep 105.761168ms before retrying.
Link reply in #188 (comment) the reason is the containerd sock on host is /run/dockershim.sock and cwagent is using /run/containerd/containerd.sock in default manifest. You need to change the one under volumes (and keep volumeMounts as it is)
I have tried applying the fix listed in this issue #188 on EKS 1.21 with the containerd runtime enabled. However, I'm still getting the same error messages:
2021-08-21T00:09:00Z W! No pod metric collected, metrics count is still 5 is containerd socket mounted? #188
2021-08-21T00:09:05Z W! [outputs.cloudwatchlogs] Invalid SequenceToken used, will use new token and retry: The given sequenceToken is invalid. The next expected sequenceToken is: 49605661750447750614958043896578931231172344896032866930
2021-08-21T00:09:05Z W! [outputs.cloudwatchlogs] Retried 0 time, going to sleep 105.761168ms before retrying.
Support for containerd runtime on EKS was added in July when EKS 1.21 was released.
https://aws.amazon.com/blogs/containers/amazon-eks-1-21-released/
This is a description of the cloudwatch daemonset on EKS 1.21 with containerd:
The text was updated successfully, but these errors were encountered: