Bug 432044 - F9-Alpha Fails to Load init with SELinux Error
Summary: F9-Alpha Fails to Load init with SELinux Error
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: rawhide
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Josef Kubin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-08 15:24 UTC by Richi Plana
Modified: 2008-02-18 15:25 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-02-18 15:05:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
audit.log with "autorelabel enforcing=0" (36.40 KB, text/plain)
2008-02-12 05:47 UTC, Richi Plana
no flags Details

Description Richi Plana 2008-02-08 15:24:07 UTC
Description of problem:

After a fresh install of F9-Alpha on an x86_64 machine, booting fails with the
following error:

/sbin/init error: error while loading shared libraries: libsepol.so.1: cannot
open shared object file: Permission denied

Kernel panic - not syncing: Attempted to kill init!


Upon rebooting with kernel option "selinux=0", booting succeeds but I saw the
following message in the screen log:

Mount failed for selinuxfs on /selinux: No such device


I'm not sure if that message was there without "selinux=0" (it scrolled by too
fast).

Comment 1 Daniel Walsh 2008-02-08 15:53:20 UTC
THis looks like a badly mislabeled system.

You can label it by adding 

autorelabel enforcing=0 

to the kernel boot line.


If this was a fresh install, and it ended up in this state, it sounds like an
anaconda bug.

Comment 2 Richi Plana 2008-02-09 05:30:07 UTC
Adding "autorelabel enforcing=0" allowed it to boot, but when I reboot it
(without changing grub.conf) and let it run with default Fedora kernel
parameters, it again locked hard with the same error.

Yes, this was a fresh install (only /home was not reformatted).

Should I refile? Or can this bug be redirected?

Comment 3 Daniel Walsh 2008-02-11 22:25:10 UTC
If you boot in permissive mode (enforcing=0) grab the audit.log and attach it.

Comment 4 Richi Plana 2008-02-12 05:47:44 UTC
Created attachment 294628 [details]
audit.log with "autorelabel enforcing=0"

Comment 5 Daniel Walsh 2008-02-18 15:05:38 UTC
Looks like it never relabeled.

fixfiles restore

Shoulod relabel it in permissive mode.  Then reboot should work.



Comment 6 Josef Kubin 2008-02-18 15:25:27 UTC
Now I'm installing F9-Alpha to test it ... result will come soon.


Note You need to log in before you can comment on or make changes to this bug.