Vector pods going into a panic state in RHOCP 4

Solution Verified - Updated -


  • Vector pods show the below log:

    WARN sink{component_kind="sink" component_id=splunk_platform_receiver component_type=splunk_hec component_name=splunk_platform_receiver}: vector::sinks::util::retries: Retrying after error. error=Failed to make HTTP(S) request: connection error: Connection reset by peer (os error 104)
    thread 'vector-worker' panicked at 'all branches are disabled and there is no else branch', src/kubernetes/
    note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
  • Vector pods are not able to collect the logs.
  • Panicked error is shown in Vector logs.


  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat Openshift Logging (RHOL)
    • 5.5
    • 5.6
    • 5.7
  • 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