kernel problem
 

Hi, I run a Centos PC which I use as a server. The PC is running headless and I mostly store office files and mp3s. FYI

2.6.32-279.19.1.el6.i686

I check /var/log/messages every morning and activity is minimal. This morning I could not open any docs. When I checked messages things started going crazy at 11:10:12 on Feb 6 (file attached). I panicked and rebooted which was probably a mistake but after the reboot the same messages appeared.

A quick flick around the net suggested there was a kernel problem affecting selinux and, as suggested, "semodule -B" would help. I tried this and the messages disappeared.

So, for now, I have a functional server. But I am way out of my depth when diagnosing this problem. I would be grateful if someone could have a look at the attached messages file and make suggestions.

Thanks

Thats a fairly generic message...but what triggered the condition is what you need to find out. You can use ausearch to look for things in the audit daemon logs. For example, to see today's AVC denials:
The man page has more options, too...worth a read. You can also disable setroubleshoot altogether, although I wouldn't without knowing what's up.
My first inclination would be to ask "what changed"?? Where is your server set up? Is it exposed to the internet at all? Did you look for any hardware faults? If this has been chugging along fine for a good while, then suddenly did something....well...something had to cause it.

thanks TB0ne. I am digging. Noted your point about "what changed". Nothing immediate springs to mind but I am racking my brains. Yup, connected to internet. No known h/w problems. I'll report back with any progress.

Well, that's why I asked about internet connectivity. If someone tried to get in (and I am NOT saying they did..just mentioning the possibility), something may have been changed for you. :) That's unlikely, though...but I'd look into the system logs for hardware related messages, and perhaps run smartctl to see if your disks are healthy.

I am going to close this one even though I haven't really got a solution. Thanks to TB0ne for some some useful tips - the disks are fine but I need to keep looking and learning.

I found I had set the server in question to run selinux in permissive mode which I have now changed.