Account Links: Cart | Your Account | Logout

Skip to content

Red Hat Knowledgebase

Red Hat Knowledgebase Search:

Updated Within the Last:

New Solutions within the last day New Solutions within the last week New Solutions within the last month

Browse by topics:


Click to View a Topic
Red Hat Enterprise Linux > SELinux > Issue <<  18 of 18 >>

Solution Tools:


Email a Solution Postcard Printer version Submit a comment on this answer Update notifications Request an answer Back

Article Reference

Article ID: 10759
Last update: 06-27-07
Issue:
Why does my system report "There is already a security framework initialized, register_security failed." when booting up?
Resolution:

When the system is booting up, the kernel may report the following error after SELinux Initializing.

SELinux: Initializing.
SELinux: Starting in permissive mode
There is already a security framework initialized, register_security failed.
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary

SELinux registered itself during the boot time, hence the service initializing and starting successfully. After this, the LSM module tries to hook-in. LSM is a framework to allow the Linux kernel to support a variety of computer security models while avoiding favoritism toward any single security implementation. LSM was designed to provide everything needed to successfully implement a mandatory access control module, while imposing the least possible changes on the Linux kernel.

However, SELinux has already taken the primary place and when LSM tries to issue register_security(), it cannot do this and thus returns EINVAL:

There is already a security framework initialized,
register_security failed.

What happens next is that SELinux registers the LSM as its secondary module:

selinux_register_security: Registering secondary module
capability Capability LSM initialized as secondary

It is only a warning message and should not be of concern.


How well did this entry answer your question?


good wrong incomplete out of date
Red Hat Enterprise Linux > SELinux > Issue <<   18  of  18  >>