Collector in CrashLoopBackOff when defined an output that not used in the pipelines in RHOL 6

Solution Verified - Updated -

Issue

  • Collector pods are going in CrashLoopBackOff state when there is unused outputs defined in the ClusterLogForwarder(CLF) in RHOL6, but not an error visible in the clusterLogForwarder custom resource status section:

    $ oc get pods -l app.kubernetes.io/component=collector -n openshift-logging
    NAME              READY   STATUS             RESTARTS       AGE
    collector-796xd   0/1     CrashLoopBackOff   33 (85s ago)   144m
    collector-bkswb   0/1     CrashLoopBackOff   33 (86s ago)   144m
    collector-gjct7   0/1     CrashLoopBackOff   33 (56s ago)   144m
    collector-htq46   0/1     CrashLoopBackOff   33 (32s ago)   144m
    collector-rnw5w   0/1     CrashLoopBackOff   33 (72s ago)   144m
    
  • Collector pods throw the error=Transform "<normalized output name> " has no inputs has no inputs error:

    $ oc logs collector-796xd 
    Creating the directory used for persisting Vector state /var/lib/vector/openshift-logging/collector
    Starting Vector process...
    2025-02-20T18:24:16.695224Z ERROR vector::cli: Configuration error. error=Transform "output_rsyslog_parse_encoding" has no inputs
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift Logging (RHOL)
    • 6
  • Vector

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content