Collector pods fails to start on nodes with IPv6 disabled

Solution Verified - Updated -

Issue

  • Collector pods crashes continuously on the node where IPv6 disabled when vector is used as log collector:

    $ oc get pods -l component=collector -n openshift-logging
NAME                                            READY   STATUS             RESTARTS      AGE
collector-25lf5                                 1/2     CrashLoopBackOff   8 (49s ago)   18m
collector-296k7                                 1/2     CrashLoopBackOff   8 (89s ago)   18m
collector-ffnll                                 1/2     CrashLoopBackOff   8 (31s ago)   18m
collector-kzwmp                                 1/2     CrashLoopBackOff   8 (64s ago)   18m
collector-lkvz7                                 1/2     CrashLoopBackOff   8 (59s ago)   18m
collector-lpznv                                 1/2     CrashLoopBackOff   8 (75s ago)   18m
collector-q5zz6                                 1/2     CrashLoopBackOff   8 (25s ago)   18m
collector-qhgh9                                 1/2     CrashLoopBackOff   8 (99s ago)   18m
collector-qs4wc                                 1/2     CrashLoopBackOff   8 (62s ago)   18m

  • Collector pods streams below logs repetitively:

    2023-10-17T16:56:32.668526Z ERROR sink{component_kind="sink" component_id=prometheus_output component_type=prometheus_exporter component_name=prometheus_output}: vector::sinks::prometheus::exporter: Failed to start Prometheus exporter: TCP bind failed: Address family not supported by protocol (os error 97)

Environment

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