Collector pods are going in CrashLoopBackOff state in RHOL 6
Issue
-
Collector pods are going in
CrashLoopBackOff
state when there isunused outputs
defined in theClusterLogForwarder(CLF)
in RHOL6.$ oc get pods -n openshift-logging | grep -i crash NAME READY STATUS RESTARTS AGE logging-clf-4z6tt 0/1 CrashLoopBackOff 5 (39s ago) 4m31s logging-clf-6mtl8 0/1 CrashLoopBackOff 5 (38s ago) 4m31s logging-clf-76lrw 0/1 CrashLoopBackOff 5 (43s ago) 4m31s logging-clf-l4zvz 0/1 CrashLoopBackOff 5 (30s ago) 4m30s logging-clf-nkzj6 0/1 CrashLoopBackOff 5 (28s ago) 4m31s logging-clf-pbns7 0/1 CrashLoopBackOff 5 (29s ago) 4m31s
-
Pod logs refer as below.
$ oc logs logging-clf-4z6tt Creating the directory used for persisting Vector state /var/lib/vector/openshift-logging/logging-clf Checking for buffer lock files /var/lib/vector/openshift-logging/logging-clf /usr/bin found lock files: '' /usr/bin Starting Vector process... 2025-01-17T21:20:06.914687Z ERROR vector::cli: Configuration error. error=Transform "output_elasticsearch_secure_external_index" has no inputs 2025-01-17T21:20:06.914707Z ERROR vector::cli: Configuration error. error=Transform "output_ocplogstore_syslogout_parse_encoding" has no inputs
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- Red Hat OpenShift Logging (RHOL)
- 6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.