Home > FAQs > Why do I get a kernel panic error relating to SELinux when installing X Window System on Centos?

Copyright (c) 2006-2014 MindTouch Inc.

This file and accompanying files are licensed under the MindTouch Master Subscription Agreement (MSA).

At any time, you shall not, directly or indirectly: (i) sublicense, resell, rent, lease, distribute, market, commercialize or otherwise transfer rights or usage to: (a) the Software, (b) any modified version or derivative work of the Software created by you or for you, or (c) MindTouch Open Source (which includes all non-supported versions of MindTouch-developed software), for any purpose including timesharing or service bureau purposes; (ii) remove or alter any copyright, trademark or proprietary notice in the Software; (iii) transfer, use or export the Software in violation of any applicable laws or regulations of any government or governmental agency; (iv) use or run on any of your hardware, or have deployed for use, any production version of MindTouch Open Source; (v) use any of the Support Services, Error corrections, Updates or Upgrades, for the MindTouch Open Source software or for any Server for which Support Services are not then purchased as provided hereunder; or (vi) reverse engineer, decompile or modify any encrypted or encoded portion of the Software.

A complete copy of the MSA is available at http://www.mindtouch.com/msa

Why do I get a kernel panic error relating to SELinux when installing X Window System on Centos?

Table of Contents


When installing the X Window System on a Centos based instance, you may encounter a kernel panic error similar to this:

audit(1317965535.759:2): enforcing=1 old_enforcing=0 auid=4294967295
Unable to load SELinux Policy. Machine is in enforcing mode. Halting now.
Kernel panic - not syncing: Attempted to kill init!

This is due to the X Window System installing SELinux as a dependency, and if it isn't needed we normally recommend simply disabling it. This article will explain how to do that.


If you are able to boot and SSH into the instance, you will want to edit the following file:


When editing this file, change:




Be sure to save the changes and exit the file. Upon reboot, you should no longer see this kernel panic message in the console output.

NOTE: You may not be able to get the instance to a stable enough state where you can edit the /etc/sysconfig/selinux file by SSH. If this is the case, we may need to get creative and setup another instance with a script that can dynamically disable SELinux. Feel free to drop us a line at support@rightscale.com or (866) 787-2253 and we'll be happy to do our best to assist.

You must to post a comment.
Last modified
21:30, 16 May 2013



This page has no classifications.



Glossary | 用語용어 Site Map | Site Help Community Corporate Site Get Support Dashboard Login
Doc Feedback Product Feedback Resources MultiCloud Marketplace Forums

Dashboard Status

© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.