Fluentd pods are failing with "permission denied" errors

Solution Verified - Updated -

Issue

  • Fluentd pods are failing with permission denied errors
  • Pod logs shows:
sed: couldn't open temporary file /etc/fluent/configs.d/sedQf05Gd: Permission denied
sed: couldn't open temporary file /etc/fluent/configs.d/openshift/sedLJE9Ld: Permission denied
sed: couldn't open temporary file /etc/fluent/configs.d/openshift/sed6j1Byd: Permission denied
WARNING: Unable to check for cri-o
rm: cannot remove '/etc/fluent/configs.d/openshift/output-operations.conf': Permission denied
  • journalctl logs shows:
Jul 10 05:16:21 cen1-ocpnod03 atomic-openshift-node[12709]: E0710 05:16:21.834033   12709 pod_workers.go:186] Error syncing pod bc4202d4-812c-11e8-8880-005056a07a77 ("logging-fluentd-klcb6_logging(bc4202d4-812c-
11e8-8880-005056a07a77)"), skipping: failed to "StartContainer" for "fluentd-elasticsearch" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=fluentd-elasticsearch pod=logging-fluentd-klcb6_loggi
ng(bc4202d4-812c-11e8-8880-005056a07a77)"

Environment

  • OpenShift Container Platform 3.9

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.