On 11/21/2020 02:50 AM, Marc Balmer via CentOS wrote: > >> Am 20.11.2020 um 19:50 schrieb lejeczek via CentOS <centos at centos.org>: >> >> hi guys >> >> I've just gotten a bunch of updates via yum and something >> weird seems to be going on after the update. >> System has: >> >> selinux-policy-3.13.1-268.el7_9.2.noarch >> selinux-policy-targeted-3.13.1-268.el7_9.2.noarch >> >> actually three different boxes, all the same: >> >> $ semodule -l >> No modules. >> >> and an attempt to install modules fails: >> >> $ semodule -i openvpn.pp >> Failed to resolve typeattributeset statement at >> /etc/selinux/targeted/tmp/modules/400/pe-openvpn/cil:1 >> semodule: Failed! > I have a smilar issue after the latest CentOS 7 update on my gitlab server: > > # semodule -l > libsemanage.semanage_direct_get_module_info: Unable to read gitlab-7.2.0-ssh-keygen module lang ext file. > semodule: Failed on list! > > I am since unable to access the gitlab server using ssh, I had to turn off selinux for using gitlab. > > Don't know, however, if the two issues are related. > > - mb > >> Does above "usual" work for you? >> many thanks, L. >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> https://lists.centos.org/mailman/listinfo/centos > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos Oddly enough, it looks like I have a similar issue when booting the latest kernel for CentOS 7 except it locks up during the boot process with the message "semodule: Failed [...]"