Description
Describe the bug
stdout P followed my infinite loop of "\\\\" in cloudwatch log stream for fluentd - I installed fluentd with container insights on an eks cluster. One out of the 4 fluentd pods has racked up over 10TB of data in 2 weeks. The other 3 pods are working as expected. The error that accounts for the majority of this data is shown in the log as stdout P followed my loads of \\\
To Reproduce
curl https://raw.githubusercontent.com/aws-samples/amazon-cloudwatch-container-insights/latest/k8s-deployment-manifest-templates/deployment-mode/daemonset/container-insights-monitoring/quickstart/cwagent-fluentd-quickstart-enhanced.yaml | sed "s/{{cluster_name}}/cluster-name/;s/{{region_name}}/cluster-region/" | kubectl apply -f -
Expected behavior
to have same amount of data roughly for other fluentd pods - other pods processed about 1-2GB
Your Environment
- Fluentd version: fluentd 1.10.3
- TD Agent version:
- Operating system: amazon-linux-2
- Kernel version:
Your Configuration
curl https://raw.githubusercontent.com/aws-samples/amazon-cloudwatch-container-insights/latest/k8s-deployment-manifest-templates/deployment-mode/daemonset/container-insights-monitoring/quickstart/cwagent-fluentd-quickstart-enhanced.yaml | sed "s/{{cluster_name}}/cluster-name/;s/{{region_name}}/cluster-region/" | kubectl apply -f -
Your Error Log
log: date:time.xxxx stdout P \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\..ect
Additional context
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status