Ubuntu 20.04 LTS – rsyslog forwarding stops after remote TLS policy update – Fix & Prevention

📖 ~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

Central logging gaps appear as rsyslog can no longer deliver events to remote collector.

Environment & Reproduction

Begins after remote endpoint enforces stronger TLS version or certificate requirements.

Root Cause Analysis

Client-side TLS config or trust chain no longer matches collector security policy.

Quick Triage

Confirm local log capture continues and assess forwarding queue backlog size.

Step-by-Step Diagnosis

Review rsyslog TLS errors, certificate validation results, and protocol negotiation output.

Solution – Primary Fix

Update rsyslog TLS settings, trust anchors, and target cipher/protocol parameters.

Solution – Alternative Approaches

Route temporarily through local relay with compatible policy while endpoints are standardized.

Verification & Acceptance Criteria

Forwarding resumes and backlog drains with no recurring TLS handshake errors.

Rollback Plan

Revert to previous transport profile if new TLS policy causes broader compatibility issues.

Prevention & Hardening

Track cert rotation schedules and validate logging pipeline TLS in change rehearsals.

Related Errors & Cross-Refs

May coincide with CA trust updates and outbound firewall policy changes.

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

View all Ubuntu 20.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

rsyslog TLS setup documentation and Ubuntu centralized logging architecture guidance.