Red Hat Bugzilla – Bug 168464
HTTP Configuration Tool Corrupts httpd.conf file
Last modified: 2015-03-04 20:15:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Description of problem:
The default httpd.conf file (I'll attach it later) works fine. The httpd service can start and stop without problem.
When you open the GUI HTTP Configuration Tool Desktop->System Settings->Server Settings->HTTP, and then do anything or nothing, and then click OK, first it asks if you want to save or exit (Yes), then (if the httpd.conf is still the default file) it asks "The configuration file has been manually modified. Overwrite?"
If you choose "Yes", then it copies the original default httpd.conf to httpd.conf.back, and writes an entirely new and different httpd.conf (I'll also attach that later).
This new httpd.conf file is corrupt somehow. As long as that new file is in place, the httpd servie will always fail to start.
There's no entries in the httpd log. The problem still occurs even when SELinux is disabled for httpd. I'll also attached the audit log.
If I move the backed-up pre-corrupted httpd.conf file back into place, then httpd can start up again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run HTTP configuration tool
2. Choose Yes to overwrite "manually edited" httpd.conf
3. Start httpd service
Actual Results: httpd service fails to start
Expected Results: It should have started
Created attachment 118895 [details]
Corrupted httpd.conf created by GUI HTTP config tool
Created attachment 118896 [details]
Good original httpd.conf file
Created attachment 118897 [details]
truncated audit log (SELinux?)
I've looked at your config file and the problem is that the Server Name has to
be a valid hostname.
Currently the tool doesn't check for this, so an invalid entry will result in an
invalid httpd.conf file.
Simply putting something like ashslinuxserver as name should work fine.
I'll see if i can fix it in one of the next versions.
Read ya, Phil
OK, found a nice way to check it with a dialog box poping up if you specified an
Fix will be in next build.
Read ya, Phil