Collector pods in CrashLoopBackOff when setting authentication to token for ElasticSearch output in RHOL6

Solution Verified - Updated -

Issue

  • Collector pods are in CrashLoopBackOff as its facing invalid configuration error when setting authentication to token for Elasticsearch output.

    $ oc get pods -l app.kubernetes.io/component=collector -n openshift-logging

NAME              READY   STATUS             RESTARTS        AGE
collector-btdkn   0/1     CrashLoopBackOff   5 (2m28s ago)   5m35s
collector-fg88w   0/1     CrashLoopBackOff   5 (2m23s ago)   5m31s
collector-fnwbq   0/1     CrashLoopBackOff   5 (2m33s ago)   5m31s
collector-jf4vg   0/1     CrashLoopBackOff   5 (2m29s ago)   5m30s
collector-kl58m   0/1     CrashLoopBackOff   5 (2m28s ago)   5m31s
collector-kpmkq   0/1     CrashLoopBackOff   5 (2m38s ago)   5m30s
collector-lmxrc   0/1     CrashLoopBackOff   5 (2m40s ago)   5m31s
collector-lvws2   0/1     CrashLoopBackOff   5 (2m43s ago)   5m30s
collector-lw7c6   0/1     CrashLoopBackOff   5 (2m46s ago)   5m31s

    $ oc logs collector-lmxrc

Creating the directory used for persisting Vector state /var/lib/vector/openshift-logging/collector
Starting Vector process...
2025-03-29T09:46:37.810680Z ERROR vector::cli: Configuration error. error=unknown variant `bearer`, expected `basic` or `aws`

in `sinks.output_elasticsearch`

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