- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
11-18-2026 01:44 PM
Hello, the following behavior is experienced on two rocky 9.8 and 9.9 Linux systems. The set both of these systems are in have 0 policies written and enabled, so, it's in "audit" mode and ideally exists somewhat silently and allows us admins to do our work, and not interrupt our users.
Account "user" is in sudoers. It can elevate to root, which results in the same output.
[user@server1 linux]$ distro
Rocky Linux 9.8
[user@server1 linux]$ sudo dnf install yazi
[epm] enter password for [user]:
[epm] try again:
[epm] no execution allowed for [dnf]
[user@server1 linux]$ sudo su -
Last login: Tue Nov 17 13:02:44 CST 2026 on pts/2
...
[root@server1~]#
[root@server1~]# dnf install yazi
[epm] no execution allowed for child command [/usr/bin/dnf]
-bash: /usr/bin/dnf: /usr/bin/python3.9: bad interpreter: Permission denied
==============================================
Account "admin" is the same as "user" from earlier. It has access to sudo privileges and can elevate to root.
[admin@server2~]$ distro
Rocky Linux 9.9
[admin@server2~]$ sudo dnf update
[epm] enter password for [admin]:
[epm] no execution allowed for [dnf]
Does ANYBODY know what is going on behind the scenes here? I am willing to do a deep dive into logs. We just want to update our systems.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

