RHEL 7 yum Metadata Expired and Mirror Timeout Errors

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

Package operations fail or stall, and application updates are delayed. Operators often see yum timeout messages while systemctl-managed service updates are pending, with useful clues in journalctl.

Environment & Reproduction

This occurs on RHEL 7 hosts using yum with one or more slow mirrors, often behind restricted firewalld egress rules. Reproduce by clearing cache and running yum makecache while SELinux is enforcing and services are active.

Root Cause Analysis

The root cause is usually stale metadata, DNS or proxy latency, or repository configuration drift. Secondary factors include blocked outbound ports in firewalld, misconfigured service proxy settings, and SELinux-labeled cache paths.

Quick Triage

Run quick checks: yum repolist all, systemctl status network, service network status, firewall-cmd –list-all, getenforce, and journalctl -xe. These confirm whether connectivity, firewall, SELinux, or repo config is the dominant fault.

Step-by-Step Diagnosis

Capture journalctl logs during yum runs, validate repo URLs, and test mirror reachability. Confirm firewalld egress policy, validate SELinux denials with audit logs, and compare service environment settings for proxy and DNS.

Solution – Primary Fix

Clean and rebuild yum metadata, pin reliable mirrors, and correct proxy or DNS settings. If needed, update firewalld rules, restore SELinux contexts, restart impacted service units with systemctl, and re-run yum transactions.

Solution – Alternative Approaches

Use a local repository mirror, Satellite content source, or short-term cached proxy. You can also schedule off-peak yum operations and isolate repo traffic with dedicated service configuration.

Verification & Acceptance Criteria

Acceptance requires successful yum update and install runs without timeout or metadata errors. Confirm with journalctl that service restarts are clean and no firewalld or SELinux blocks remain.

Rollback Plan

If changes cause regressions, restore previous repo files and proxy settings from backup. Undo package changes with yum history, revert firewalld adjustments, and restore prior SELinux policy state.

Prevention & Hardening

Standardize repo definitions, add mirror health checks, and monitor yum latency. Keep firewalld policy explicit, keep SELinux enforcing with correct labels, and centralize service and journalctl alerting.

Related Errors & Cross-Refs

Common related errors include rpmdb lock messages, GPG validation failures, and dependency conflicts. See linked tutorial 9051 for baseline repo management workflow on RHEL 7.

Related tutorial: View the step-by-step tutorial for rhel-7.

View all rhel-7 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Consult man yum, man yum.conf, man systemctl, man service, man firewall-cmd, man selinux, and man journalctl for command details and operational guidance.