[rear-users] Newbie: Selinux issues - kernel panic

Gratien D'haese gratien.dhaese at it3.be
Thu Nov 27 14:49:44 CET 2014


sorry for the late answer - if you check /etc/rc.d/rc.sysinit
then you will see a section about relabeling: 

# If relabeling, relabel
mount points.
if [ -n "$SELINUX_STATE" -a "$READONLY" != "yes" ]; then

if [ -f /.autorelabel ] || strstr "$cmdline" autorelabel ; then

restorecon $(awk '!/^#/ && $4 !~ /noauto/ && $2 ~ /^// { print $2 }'
/etc/fstab) >/dev/null 2>&1

So, if /.autorelabel has been set
(as in your case) then autorelabel should kick in. Otherwise, you can
append the string "autorelabel" on command line during booting.


On Wed, 19 Nov 2014 14:44:59 +0000, Brian Ipsen 

 Probably a question, that has been seen before - but even
though I've googled for more than an hour and truied to find a solution,
my test recovery is still not running... 

I have configured REAR to use
TSM as backup system - and create a boot cd. 

When booting on the CD,
it looks like evrything regarding the restore of files goes OK. 

when booting after the restore, the kernel ends up in panic. I found
out, that I can boot, if I add selinux=0 to the boot options - but this
does not solve my issue with selinux... 

There is a file named
/.autorelabel on the recovery host - but aparently this does not trigger
the relabeling process in selinux... 

I'm trying on CentOS 6.6 ...

Any hints on where to troubleshoot or how to fix the issue ? 




Gratien D'haese
IT3 Consultants bvba 
Vennestraat 15,
B-2560 Nijlen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pikachu.3ti.be/pipermail/rear-users/attachments/20141127/9f592c2a/attachment.html>

More information about the rear-users mailing list