This discussion is archived
2 Replies Latest reply: Sep 21, 2012 7:34 AM by tbrinkmann RSS

OL 5.8(VM) hung on boot up after SELinux

tbrinkmann Explorer
Currently Being Moderated
Hi,
I´s me again :-/ after I successful update all our OL5.8 systems I have a problem with only one machine.

I updates our systems with yum update to latest 5.8 and reboot with kernel uek-300 the. The Updated systems are running fine without any problems.

After a cluster crash only one system does not start anymore. I Repeat the first restart after the updates was OK. But now the system hungs after some SELinux information.
_________________________________________________________
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: class peer not defined in policy
SELinux: class capability2 not defined in policy
SELinux: class kernel_service not defined in policy
SELinux: class tun_socket not defined in policy
SELinux: permission open in class dir not defined in policy
SELinux: permission open in class file not defined in policy
SELinux: permission open in class chr_file not defined in policy
SELinux: permission open in class blk_file not defined in policy
SELinux: permission open in class sock_file not defined in policy
SELinux: permission open in class fifo_file not defined in policy
SELinux: permission recvfrom in class node not defined in policy
SELinux: permission sendto in class node not defined in policy
SELinux: permission ingress in class netif not defined in policy
SELinux: permission egress in class netif not defined in policy
SELinux: permission module_request in class system not defined in policy
SELinux: permission setfcap in class capability not defined in policy
SELinux: permission nlmsg_tty_audit in class netlink_audit_socket not defined in policy
SELinux: permission forward_in in class packet not defined in policy
SELinux: permission forward_out in class packet not defined in policy
SELinux: the above unknown classes and permissions will be allowed
type=1403 audit(1348214944.705:2): policy loaded auid=4294967295 ses=4294967295
__________________________________________________________

I googled about that and there are some entries about mounting problems.
To check the domU fstab we mount the domU system partition to our dom0 but we see no problems there.

The system is a OL5.8 VM on OVM 2.2.2.
Does anyone can give a hint how to dig this out ?

thanks again :-/ *T

update: we disable selinux system also stuck...

Edited by: tbrinkmann on Sep 21, 2012 5:35 AM

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points