-
Bug
-
Resolution: Unresolved
-
Blocker
-
Logging 6.4.3
-
Quality / Stability / Reliability
-
1
-
False
-
-
False
-
NEW
-
NEW
-
Release Note Not Required
-
-
-
Logging - Sprint 285
Description of problem:
There is error starting journald process. Looks to be systemd binary is missing under collector.
Collector logs:
oc logs pod/collector-vcftb -c collector --tail=25
Creating the directory used for persisting Vector state /var/lib/vector/syslog-aosqe/collector
Starting Vector process...
2026-03-10T02:40:07.586505Z ERROR source
2026-03-10T02:40:08.588269Z ERROR source{component_kind="source" component_id=input_my_infra_journal component_type=journald}
: vector::internal_events::journald: Internal log [Error starting journalctl process.] is being suppressed to avoid flooding.
2026-03-10T02:40:17.607657Z ERROR source
: vector::internal_events::journald: Internal log [Error starting journalctl process.] has been suppressed 9 times.
Version-Release number of selected component (if applicable):
6.4.3
How reproducible:
Always
Steps to Reproduce:
- Deploy CLO and LO v6.4.3
- Forwards infra logs out
- Check collector logs
Actual results:
journald logs are not collected due to missing systemd binary?
Expected results:
journald logs should be collected
Additional info:
Similar issue
- clones
-
LOG-8902 Collector is unable to collect journald logs
-
- Verified
-
- links to