CentOS Stream 9 – Common Problem 234 – 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

Users cannot login after AD rename

Environment & Reproduction

Hostname or AD object rename leaves stale SSSD cache.

Root Cause Analysis

Cached LDAP entries and Kerberos tickets reference old principal.

Quick Triage

id and sssctl domain-status to confirm.

Step-by-Step Diagnosis

Run: sudo sssctl cache-expire -E; sudo klist -k /etc/krb5.keytab.

Solution – Primary Fix

sudo systemctl stop sssd; sudo rm /var/lib/sss/db/*; sudo realm leave && realm join.

Solution – Alternative Approaches

Re-enroll with adcli update –add-samba-data –domain=.

Verification & Acceptance Criteria

id returns the correct UID and getent passwd succeeds.

Rollback Plan

Restore /var/lib/sss/db backup and previous /etc/krb5.keytab.

Prevention & Hardening

Automate AD join with Ansible role and rotate keytab via scheduled job.

Related Errors & Cross-Refs

Pairs with PAM error 4 and GSSAPI keytab not found errors.

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

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

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

SSSD admin guide and realmd(8).