Fedora Linux Support Community & Resources Center
  #1  
Old 6th December 2009, 12:57 AM
theAdmiral Offline
Registered User
 
Join Date: Nov 2008
Posts: 495
linuxfedorafirefox
SELinux Error

Since my new install of F12KDE, I have been getting various SELinux errors. I will attempt to address them, and resolve them, one-by-one.

The one that popped up today is as follows:

Quote:
SELinux denied access requested by prelink. /var/lib/misc/prelink.quick may be a

mislabeled. /var/lib/misc/prelink.quick default SELinux type is

prelink_var_lib_t, but its current type is cron_var_lib_t. Changing this file

back to the default type, may fix your problem.
I looked at the specified location, in the specified file, and found only one line. It was a time stamp for yesterday. There was nothing else in the file. Does anybody know how to fix this, please?

Thank you much,
__________________
---------------------------------------------------------
Dual-boot
System: HP Pavilion dv6500 Notebook PC Rev. 1
Intel(R) Core(TM)2 Duo CPU T7500 @2.2GHz
Number of CPUs: 2 (32-bit)
System Memory: 3072MB
Fedora 16 KDE Verne
Windoze 7, SP1

System: Sony Vaio
Intel (R) Pentium (R) 4 CPU 2.8 GHz
System Memory: 992 MB RAM
Fedora 16
Reply With Quote
  #2  
Old 6th December 2009, 01:58 AM
PabloTwo Online
"Registered User" T-Shirt Winner
 
Join Date: Mar 2007
Location: Seville, FL
Posts: 5,854
linuxfedorafirefox
What's in the file is of no importance or concern relating to the SELinux error message. The file has the wrong SELinux context assigned, as stated in the error message you posted. To see the SELinux context of a file, use the -Z option to the ls command:
Code:
BASH:~/-> ls -Z /var/lib/misc/prelink.quick
-rw-r--r--. root root system_u:object_r:prelink_var_lib_t:s0 /var/lib/misc/prelink.quick
When you get those SELinux troubleshoot warnings and the star icon appears on the panel, click on the star to see the information. Go to the most recent incident, or the one that involves the incident you're interested in, and then click on the "see more info" button. Scroll down in that and it will almost always show you the command to "fix" the problem.

In this case you need to relabel the SELinux security context of that file, so the command would be:

sudo chcon -t prelink_var_lib_t /var/lib/misc/prelink.quick

You can also fix SELinux context mislabelled files system wide by doing:

sudo touch /.relabel

then rebooting.... and SELinux will scan the entire file system and apply correct labelling early in the boot process.

Last edited by PabloTwo; 6th December 2009 at 02:02 AM.
Reply With Quote
  #3  
Old 15th December 2009, 11:43 PM
dishawjp Offline
Registered User
 
Join Date: Mar 2004
Location: Central NY
Age: 61
Posts: 477
linuxfedorafirefox
I had a similar issue with SELinux and /var/lib/misc/prelink.force

In my case, the file did not exist! No biggie though, as root I did a
Code:
touch /var/lib/misc/prelink.force
restorecon '/var/lib/misc/prelink.force'
and then opened the empty file with vi and just copied the contents (a time stamp) from prelink.full into prelink.force.

End of problem.

HTH

Jim Dishaw
__________________
Registered Linux User 294493
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
SELinux Error about VLC astrobob Using Fedora 2 27th February 2009 11:23 PM
SELinux error with F9-Preview Gul Dukat Alpha - Beta (Fedora 9 Only) 10 12th May 2008 09:58 PM
SELinux error with apcupsd catalinsanda Security and Privacy 0 14th June 2007 10:50 PM
Selinux error mebrelith Using Fedora 2 14th January 2005 05:10 PM


Current GMT-time: 03:12 (Sunday, 20-04-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat