Ubuntu 22.04 LTS High CPU in journald from Excessive Service Logging

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

systemd-journald consumes significant CPU and disk I/O, reducing host performance. Application latency increases as logging storms saturate journaling pipeline.

Environment & Reproduction

Ubuntu 22.04 LTS host runs noisy service with debug logging enabled in production. Reproduce by generating rapid repeated errors or verbose loop logging.

Root Cause Analysis

Journald is optimized but can become bottleneck under extreme message rates. Unlimited debug logs and insufficient rate limiting cause sustained high processing overhead.

Quick Triage

Identify top CPU processes and estimate log volume from problematic unit before altering global journald settings.

Step-by-Step Diagnosis

Correlate journald load with service bursts, inspect current journald limits, and review unit-level log verbosity options that can be reduced safely.

Solution – Primary Fix

Reduce service log level, configure journald rate limits and storage caps, then restart impacted services to lower logging pressure and recover CPU headroom.

Solution – Alternative Approaches

Forward logs to external collector, use rsyslog with filtering, or implement application-side structured logging and sampling for noisy code paths.

Verification & Acceptance Criteria

journald CPU returns to baseline, message rates stay below throttle thresholds, and critical logs remain available without excessive drops.

Rollback Plan

Restore previous journald.conf, restart journald, and re-enable prior service log level if troubleshooting requires temporary verbosity.

Prevention & Hardening

Define production logging policies, limit debug mode duration, and monitor journal growth plus per-unit message rates for anomaly detection.

Related Errors & Cross-Refs

Related to disk pressure from oversized journals, service restart loops generating repeated stack traces, and absent log retention policies.

Related tutorial: View the step-by-step tutorial for Ubuntu 22.04 LTS.

View all Ubuntu 22.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Use systemd-journald.service(8), journald.conf(5), and Ubuntu logging best practices for durable and efficient observability setup.