SE alert

[jd1008]

On 07/19/2015 07:00 PM, Ed Greshko wrote:
> On 07/20/15 08:47, jd1008 wrote:
>>
>> On 07/19/2015 05:45 PM, Ed Greshko wrote:
>>> On 07/20/15 07:31, jd1008 wrote:
>>>> On 07/18/2015 09:18 PM, Ed Greshko wrote:
>>>>> On 07/19/15 11:12, Ed Greshko wrote:
>>>>>> If they are enabled, disable them for the time being and check to see if the sealerts cease.
>>>>> I should have said "stop" and "disable" them.
>>>>>
>>>> Done! and problem solved!!!
>>>> Thanx a lot!!!
>>>> Much appreciated!!!
>>> Well, it didn't "solve" the problem.  It masked it.  Those services run just fine here and elsewhere.
>>>
>> If I re-enable them and the problem returns, then I have to look elsewhere
>> as to the real cause of the problem - but I would still disable them.
>>
>>
> Did you check the label on /usr/lib64/sa/sa1  ?
>
> You could also consider going through a relabel of your entire system.  I've not run into problems with selinux but I've know others who have done things which, over time, necessitated a relabel as opposed to playing whack-a-mole.
>
> You choice, but just like rust spots on a car, problems plastered over often cause greater headaches later.
>   
I forgot the file I touch in / to force a relabel, something like 
.relabel=true ???