This reference covers frequently-encountered AlmaLinux/Rocky Linux-specific error messages and their typical resolutions — a quick-reference companion to the more general Common Linux Error Messages Explained.
"Nothing to do" / "No match for argument" (dnf)
sudo dnf clean all
sudo dnf makecacheOften indicates stale repository metadata, or that the package genuinely isn't available in any currently-enabled repository — check whether EPEL or another additional repository (see Understanding EPEL and Additional Repositories for AlmaLinux/Rocky Linux) is needed for that specific package.
"Permission denied" Despite Correct File Permissions (SELinux)
ls -Z /path/to/filesudo restorecon -Rv /path/to/fileA very common AlmaLinux/Rocky Linux-specific gotcha — standard Unix permissions being correct doesn't guarantee SELinux allows the access; check and restore the appropriate SELinux context.
"Failed to start" a Service Despite Correct Configuration
sudo journalctl -xe -u servicenamesudo ausearch -m avc -ts recentCheck both systemd logs and SELinux denials — on this distribution family, a "correctly configured" service can still fail to start due to an SELinux policy restriction not present on other distributions.
"Firewall is not running" / Connections Blocked Unexpectedly
sudo systemctl status firewalldSee How to Troubleshoot Common firewalld Errors for comprehensive firewalld-specific troubleshooting.
"Public key for package.rpm is not installed" (GPG Verification Failure)
sudo rpm --import /path/to/RPM-GPG-KEYOccurs when installing from a repository whose GPG key hasn't been properly imported — import the correct key from a trustworthy source rather than bypassing verification with --nogpgcheck.
"Transaction check error: file conflicts" During dnf Install
Indicates two packages both trying to provide the same file — often occurs when mixing packages from incompatible repository sources; check whether you have duplicate/conflicting repositories providing overlapping packages.
Kernel Panic on Boot After an Update
See How to Troubleshoot a VPS That Won't Boot After a Kernel Update — the general troubleshooting approach applies; use the GRUB menu to boot a previous kernel version while investigating.
"Could Not Resolve Host" During dnf Operations
cat /etc/resolv.confVerify DNS resolution is working at the OS level — a dnf-specific symptom of an underlying network/DNS configuration issue, not specific to package management itself.
SELinux Preventing a Specific Application Action
See How to Configure SELinux Policies for a Custom Application for the systematic approach to diagnosing and resolving SELinux-specific application blocking.
"No space left on device" Despite df Showing Free Space
df -iCheck inode usage separately from disk space usage — exhausted inodes (common with many small files) produce this error even when raw disk space appears available; same underlying issue as covered generally in How to Fix "No Space Left on Device" Errors.
Continue Reading
- Understanding SELinux Basics on AlmaLinux/Rocky Linux
- How to Troubleshoot Common firewalld Errors
- How to Use dnf: The Package Manager for AlmaLinux & Rocky Linux
Browse more articles in AlmaLinux & Rocky Linux.
