Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-7601

[release-6.0] vector panic due to Timestamp out of range - cherry-pick request for vectordotdev#20780

XMLWordPrintable

    • Incidents & Support
    • False
    • Hide

      None

      Show
      None
    • False
    • NEW
    • NEW
    • Hide
      Before this update, a log record with a malformed timestamp caused the Vector agent to panic repeatedly when attempting to forward logs to Loki. With this update, error handling for out-of-range timestamp values has been improved, which resolves the issue and allows Vector to process these logs without crashing.
      Show
      Before this update, a log record with a malformed timestamp caused the Vector agent to panic repeatedly when attempting to forward logs to Loki. With this update, error handling for out-of-range timestamp values has been improved, which resolves the issue and allows Vector to process these logs without crashing.
    • Bug Fix
    • Logging - Sprint 276
    • Critical

      Description of problem:

      Vector panics and ends up in CrashLoopBackOff, with the following trace:

      $ oc -n openshift-logging logs collector-q5hgc
2025-07-22T06:07:46.285044293Z Creating the directory used for persisting Vector state /var/lib/vector/openshift-logging/collector
2025-07-22T06:07:46.286758472Z Starting Vector process...
2025-07-22T06:07:46.686681923Z 2025-07-22T06:07:46.686630Z  WARN vector::config::loading: Transform "output_default_lokistack_route._unmatched" has no consumers
2025-07-22T06:07:48.892448681Z thread 'vector-worker' panicked at src/sinks/loki/sink.rs:256:68:
2025-07-22T06:07:48.892448681Z Timestamp out of range
2025-07-22T06:07:48.892448681Z note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2025-07-22T06:07:48.895109349Z 2025-07-22T06:07:48.895071Z ERROR sink{component_kind="sink" component_id=output_default_lokistack_application component_type=loki}: vector::topology: An error occurred that Vector couldn't handle: the task panicked and was aborted.

      Version-Release number of selected component (if applicable):

      • OpenShift Logging 6.2.3

      Actual results:

      • Vector panics and ends up in CrashLoopBackOff state: 
        $ oc -n openshift-logging get pod collector-q5hgc
NAME              READY   STATUS             RESTARTS   AGE
collector-q5hgc   0/1     CrashLoopBackOff   9          24m

      Expected results:

      Additional info:

              vparfono Vitalii Parfonov
              rhn-support-rsandu Robert Sandu
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: