On 09/29/2012 06:59 AM, Daniel J Walsh wrote:
>
> Sometimes those reports are worth reading...
>
Yes, yes they are.
I should have piped it to less.
The specific solution was at the top where it's the first thing
the reader sees in a pager like less or in the GUI selinux
debugger. This is the c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/28/2012 02:55 PM, Kevin H. Hobbs wrote:
>> From: Jack Craig doesnt the selinux
>> troubleshooter offer suggestions?
>
> I'm a bit embarrassed to admit that other than the very general boolians
> that "sudo sealert -l $UUID" suggests setting at
On Fri, Sep 28, 2012 at 11:55 AM, Kevin H. Hobbs wrote:
> > From: Jack Craig
> > doesnt the selinux troubleshooter offer suggestions?
>
> I'm a bit embarrassed to admit that other than the very general boolians
> that "sudo sealert -l $UUID" suggests setting at the end of it's output,
> it also
> From: Jack Craig
> doesnt the selinux troubleshooter offer suggestions?
I'm a bit embarrassed to admit that other than the very general boolians
that "sudo sealert -l $UUID" suggests setting at the end of it's output,
it also suggested a very specific fix at the top of it's output way off
my t
doesnt the selinux troubleshooter offer suggestions?
On Fri, Sep 28, 2012 at 11:25 AM, Kevin H. Hobbs wrote:
> I just replaced the machine that runs ganglia.
>
> httpd is being prevented from connecting to gmond.
>
> All that is displayed is:
>
> There was an error collecting ganglia data (127.
I just replaced the machine that runs ganglia.
httpd is being prevented from connecting to gmond.
All that is displayed is:
There was an error collecting ganglia data (127.0.0.1:8652): fsockopen
error: Permission denied
There's a message in /var/log/messages that blames selinux every time I
loa
