From: fedora-list-bounces@redhat.com [mailto:fedora-list-bounces@redhat.com]On Behalf Of Alexander Dalloz Sent: Wednesday, November 02, 2005 5:38 PM To: For users of Fedora Core releases Subject: Re: Apache Httpd on FC4 screwed up? FrontPage will not work w/ochanges.
Am Do, den 03.11.2005 schrieb Daniel B. Thurman um 1:16:
More information: The /etc/init.d/httpd script was replaced with that from the FC2 and it all now works right. Something major is going on with the latest updates and is preventing FrontPage from being installed so I wonder what the deal is.
Dan
You are breaking your system! It would have been much better to be SElinux aware and have read about it. For instance if you run
apachctl -v | cat
with the apachectl script that ships with FC4 you will get the output you desires.
Ok, so my "problems" started because I had SElinux running and somehow I do not have it properly configured so that the apachectl/htppd scripts would work correctly, is that it?
I tested this theory out by restoring the original scripts and adding selinux=0 to grub, rebooted, and everything worked like a charm.
Ok, so if I wanted to restore SElinux capability so that httpd would properly start up, what is it that I need to do, or if you want me to RTFM, can you provide me a starting place? What I noticed was that under SElinux, the httpd failed to run because of something regarding port 8090 for which FrontPage uses as a Virtual Server in that the httpd daemon did not have the permissions to create this port/socket and so httpd daemon failed to start.
Until I can figure this out, I will have my box running w/o SElinux. Thanks for pointing this out.
Alexander
--
Hi
Ok, so my "problems" started because I had SElinux running and somehow I do not have it properly configured so that the apachectl/htppd scripts would work correctly, is that it?
It might be that or it might be that the SELinux policies need to be changed to accomodate something you were doing which does not enhance the security risk
I tested this theory out by restoring the original scripts and adding selinux=0 to grub, rebooted, and everything worked like a charm.
You might want to disable SELinux protection for only http while you go further and get your problems sorted out. This is accomplished using SELinux booleans or toggles.
For Apache, read this http://fedora.redhat.com/docs/selinux-apache-fc3/sn-debugging-and-customizin...
Until I can figure this out, I will have my box running w/o SElinux. Thanks for pointing this out.
You can also post the AVC denied messages from /var/log/audit (if you have audit deamon enabled) or /var/log/messages
regards Rahul
Hi
Until I can figure this out, I will have my box running w/o SElinux. Thanks for pointing this out.
You can also post the AVC denied messages from /var/log/audit (if you have audit deamon enabled) or /var/log/messages
Forgot to add, these should go into the fedora-selinux list
regards Rahul