CentOS Stream 10 – Common Problem 122 – Diagnosis and Fix

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

Service cannot read or write files after restore or migration.

Environment & Reproduction

Common after restoring backups without preserving SELinux contexts.

Root Cause Analysis

Files carry default_t or unconfined_u contexts instead of the service domain.

Quick Triage

Run ls -Z and matchpathcon to compare expected vs actual labels.

Step-by-Step Diagnosis

Capture denials via ausearch -m AVC –raw -ts recent.

Solution – Primary Fix

Apply restorecon -R against the affected path tree.

Solution – Alternative Approaches

Use semanage fcontext -a then restorecon for custom paths.

Verification & Acceptance Criteria

ls -Z returns service-specific contexts and AVC denials stop.

Rollback Plan

Revert with restorecon to previous saved policy if regressions appear.

Prevention & Hardening

Include SELinux contexts in backup and restore tooling.

Related Errors & Cross-Refs

Linked to httpd, mysqld, and container_file_t domains.

Related tutorial: View the step-by-step tutorial for centos-stream-10.

View all centos-stream-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Red Hat SELinux user guide and policycoreutils docs.