Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Defaults in /etc/httpd/conf.d/system-config-httpd.conf conflicts with httpd startup (/etc/rc.d/init.d/httpd): pid file in system-config-httpd.conf points to /var/run/httpd vs. other scripts referencing /var/run/httpd/httpd.pid Net result is that service httpd fails to stop, status or restart properly. Version-Release number of selected component (if applicable): system-config-httpd-1.4.4-4.fc11.noarch How reproducible: Totally. Steps to Reproduce: 1. service httpd stop 2. 3. Actual results: httpd daemons are still running. Expected results: They should have been stopped. Additional info:
Thanks for this report, now that I understand what's been causing my problems, here's a quick and simple Workaround - define PIDFILE in /etc/sysconfig/httpd, sourced by the rc httpd script, as follows: # added 10/1/2009, by Rob Robason # The following is a workaround to https://bugzilla.redhat.com/show_bug.cgi?id=515331: PIDFILE=/var/run/httpd.pid # Of course, this will have to be undone when the bug fix is installed. This allows service(8) and telinit(8) to behave as expected.
The init script for httpd is located in the httpd component itself though, so reassigning the bug. Thanks & regards, Phil
I don't see an httpd bug here. If system-config-httpd is writing a PidFile directive to /etc/httpd/conf.d/system-config-httpd.conf as the reporter claims, which differs to the httpd.conf default - this is a system-config-httpd bug. Reporter, can you confirm this is correct?
Yes that's correct. I didn't see the option for system-config-httpd when I originally filed the bug report. My bad.
Doh, ye, now i see it. Hm, maybe we should remove the whole Server Tab from s-c-h actually as it contains settings that probably should only be modified in /etc/httpd/conf/httpd.conf. I'll try to get a fixed version out in the next few weeks, most likely completely dropping the Server tab and removing LockFile, PidFile, User, Group and CoreDumpDirectory settings in turn. Thanks & regards, Phil
OK, thanks - reassigned.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Thats done with the latest updates for F-12, F-13 and rawhide. I've removed quite a few more of those global settings and mainly just do vhost setup now in the system-config-httpd.conf file as one would expect. There might be still occasional cases where things can break, but most of that is basically not fixable as i'd need a proper httpd.conf parser for that. Thanks & regards, Phil