Friday, 3 February 2017

Error: libsemanage.semanage_direct_remove_key: Unable to remove module radius_custom at priority 400. (No such file or directory).

The other day I received the following error message when attempting to disable a custom SELinux policy - semodule -r radius_custom

libsemanage.semanage_direct_remove_key: Unable to remove module radius_custom at priority 400. (No such file or directory).
semodule:  Failed!

Clearly it will looking in the wrong place for the module (in hindsight I should have used strace to attempt to work out where it was trying to access) - although I ended up having to manually move the module from:

mv /etc/selinux/targeted/active/modules/400/radius_custom /etc/selinux/targeted/active/modules/disabled

and then reload the policies with:

semodule -R

0 comments:

Post a comment