aeolus-configure failure on fresh F16 install

Matt Wagner matt.wagner at redhat.com
Mon Jun 4 21:22:50 UTC 2012


On Mon, Jun 04, 2012 at 05:07:38PM -0400, John Eckersberg wrote:
> 
> Are you able to run this manually?:
> 
> /usr/sbin/setsebool -P httpd_can_network_connect 1

Ha! I think "-P" in particular is the killer.

After having run aeolus-configure previously, httpd_can_network_connect
was already enabled, but... Compare with and without the -P (updating
the policy values on disk, per the man page):


[root at dell-pe1855-02 ~]# getsebool httpd_can_network_connect
httpd_can_network_connect --> on
[root at dell-pe1855-02 ~]# time /usr/sbin/setsebool
httpd_can_network_connect 1

real	0m0.042s
user	0m0.001s
sys	0m0.020s
[root at dell-pe1855-02 ~]# time /usr/sbin/setsebool -P
httpd_can_network_connect 1

real	5m47.264s
user	5m32.787s
sys	0m1.775s
[root at dell-pe1855-02 ~]# 


FWIW, it sits at about 100% CPU usage -- pegging one of the four cores
on this box (and using 244 MB resident memory) -- while it runs.

You mentioned this on IRC, but to keep the list updated,
https://bugzilla.redhat.com/show_bug.cgi?id=811656 looks like the same
issue we're seeing.

-- Matt



More information about the aeolus-devel mailing list