Bug 689121

Summary: SELinux makes boot fail/hang
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: rsyslogAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED DUPLICATE QA Contact: Ben Levenson <benl>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rawhideCC: dwalsh, misek, mschmidt, sangu.fedora, theinric
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-21 10:11:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Horst H. von Brand 2011-03-19 17:06:13 UTC
Description of problem:
After the update yesterday the machine would hang in graphical boot. Disabling graphical boot it turns out NetworkManager fails starting, other stuff just seems to hang. Adding "selinux=0" to the kernel command line makes the boot work fine.

Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.9.16-5.fc15.noarch

How reproducible:
Always

Steps to Reproduce:
1. Boot...
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Vaclav "sHINOBI" Misek 2011-03-19 19:42:45 UTC
The same behaviour for me, bugs #689097 and #689098 seems to be related. Setting permissive mode is enough to make system working again.

Comment 2 Vaclav "sHINOBI" Misek 2011-03-19 20:22:11 UTC
The problem is created by rsyslog-5.7.9-1.fc15 in my case. Horst can you try to run yum downgrade rsyslog and then try to reboot if it fixes the problem for you?

Comment 3 Horst H. von Brand 2011-03-19 23:03:18 UTC
(In reply to comment #2)
> The problem is created by rsyslog-5.7.9-1.fc15 in my case. Horst can you try to
> run yum downgrade rsyslog and then try to reboot if it fixes the problem for
> you?

Yes, that fixes it.

Comment 4 Horst H. von Brand 2011-03-19 23:21:43 UTC
In view of comment 2, moving over to rsyslog

Comment 5 Horst H. von Brand 2011-03-19 23:42:47 UTC
I checked various /var/log files with SELinux enabled, and sure enough /var/log/messages contains nothing whatsoever for this boot. systemctl says:

rsyslog.service           loaded active   running       System Logging Service
rsyslogd.service          error  inactive dead          rsyslogd.service

(Sorry, didn't drill deeper into this before seeing comment 2).

Comment 6 Michal Schmidt 2011-03-21 10:11:56 UTC

*** This bug has been marked as a duplicate of bug 689089 ***