Fail2ban Does Not Ban Hosts Due to Journal Backend Misconfig

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

Brute-force attempts continue without source bans.

Environment & Reproduction

Service logs to journald while fail2ban reads wrong log path backend.

Root Cause Analysis

Jail configuration backend mismatch prevents filter matches.

Quick Triage

Run fail2ban-client status and test regex against actual journal entries.

Step-by-Step Diagnosis

Validate backend=systemd, filter definitions, and banaction integration.

Solution – Primary Fix

Set correct backend and restart fail2ban; verify firewalld actions trigger.

Solution – Alternative Approaches

Use sshd MaxAuthTries and firewall rich rules for baseline protection.

Verification & Acceptance Criteria

Offending IPs appear in jail ban list after threshold reached.

Rollback Plan

Restore previous jail.local and restart service.

Prevention & Hardening

Version-control jail configs and test against sample logs pre-deploy.

Related Errors & Cross-Refs

No failures found, jail running but no bans.

Related tutorial: View the step-by-step tutorial for oracle-linux-10.

View all oracle-linux-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Fail2ban documentation for systemd backend and Oracle Linux integration.