-
Bug
-
Resolution: Unresolved
-
Blocker
-
Logging 6.2.9
-
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:
2026-03-10T02:25:49.121666Z ERROR source{component_kind="source" component_id=input_infrastructure_journal component_type=journald}: vector::internal_events::journald: Error starting journalctl process. error=journalctl failed to execute: No such file or directory (os error 2) error_type="command_failed" stage="receiving" internal_log_rate_limit=true 2026-03-10T02:25:50.123543Z ERROR source{component_kind="source" component_id=input_infrastructure_journal component_type=journald}: vector::internal_events::journald: Internal log [Error starting journalctl process.] is being suppressed to avoid flooding. 2026-03-10T02:25:59.136167Z ERROR source{component_kind="source" component_id=input_infrastructure_journal component_type=journald}: vector::internal_events::journald: Internal log [Error starting journalctl process.] has been suppressed 9 times. 2026-03-10T02:25:59.136179Z ERROR source{component_kind="source" component_id=input_infrastructure_journal component_type=journald}: vector::internal_events::journald: Error starting journalctl process. error=journalctl failed to execute: No such file or directory (os error 2) error_type="command_failed" stage="receiving" internal_log_rate_limit=true
Version-Release number of selected component (if applicable):
6.2.9
How reproducible:
Always
Steps to Reproduce:
- Deploy CLO and LO v6.2.9
- Forwards logs to LokiStack for all tenants including infra.
- 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
- is cloned by
-
-
- POST
-
- links to
