17
10
2007
Enforcing mode requested but no policy loaded. Halting now.
Posted by: major in Emergency, Kernel Panics, SecurityHere’s a pretty weird kernel panic that I came across the other day:
Enforcing mode requested but no policy loaded. Halting now.
Kernel panic - not syncing: Attempted to kill init!
This usually means that you’ve set SELINUX in enforcing mode within /etc/sysconfig/selinux or /etc/selinux/selinux.conf but you don’t have the appropriate SELINUX packages installed. To fix the issue, boot the server into the Red Hat rescue environment and disable SELINUX until you can install the proper packages that contain the SELINUX targeted configuration.
This kernel panic appeared on a Red Hat Enterprise Linux 4 Update 5 server.
Entries (RSS)
If you have serial console or KVM to the box, you can pass selinux=0 in the boot param if you don’t want to boot up into rescue system.
Ref:
http://danwalsh.livejournal.com/3144.html
Sai
I’ve just had this problem recovering a clients RHEL 4 system from a backup.
I didn’t think they would want SELinux disabled on their O/S so i dig about in the startup scripts and noticed that it referenced files in the /selinux directory which seemed to be a selinuxfs filesystem type, this was not backed up and I’m guessing because it showed up as a mounted filesystem was excluded from the backup.
When I restored their / directory, the /selinux directory was not recreated, recreating the /selinux directory (just by doing `mkdir /selinux`) and rebooting fixed the problem and left SELinux enabled on their server.