Debug CrashLoopBackoff Fluentd pod

Environment

• Red Hat Openshift Container Platform

  • 3.x

Issue

• Fluentd pod never starts and it's in CrashLoopBackoff status.

Resolution

• To debug the Fluentd pod in failing status, run the following command as an admin user:

$ oc debug pod/failing-fluentd-pod

• This will start a copy of the failing Fluentd pod, after it starts, run inside the container:

$ bash -x run.sh

• This will run the run.sh script, which is the command Fluentd runs every time it boots.

• This script will stop and return the exit code in the same exact step it's failing when starting.

• Now, proceed to solve the underlying issue.

Root Cause

• N/A

Diagnostic Steps

• Fluentd pod is in CrashLoopBackoff and never starts.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.