-
Notifications
You must be signed in to change notification settings - Fork 14
httpd 2.4.33 fails to start on EL 6 due to invalid PidFile location #19
Comments
I think this is related to #18, can you update to 2.4.33-2 and see if that resolves the issue? |
I did try the rpm's directly as my mirrors hadn't updated and that didn't work. To make sure I spun up a docker and installed from the repo and it still fails sadly:
Even though it shows ok when it start command is issue it's actually still failing as the pid is not created in the non existent directory and it's not actually started. |
Hi, 2.4.33-2 fix that issue. I check with both centos6 and centos7 :) |
Tracked down the issue, it's not related to my goof up in #18. Fedora and RHEL have traditionally added in the filesystem layout via patch. The Working on fixing this now, thanks for opening the issue! |
Just hit this issue as well, thanks for looking in @carlwgeorge |
Hey
Not completely sure if this is a repo or a direct apache issue but I noticed that httpd was failing to start today on some Centos 6 machines after the update to 2.4.33.
Turns out the PidFile setting has changed from
/var/run/httpd/httpd.pid
to/run/httpd/httpd.pid
between 2.4.29 and 2.4.33 somehow although I can't see exactly why after quickly looking both at apache's and this source.Nonetheless this means httpd will always fail on Centos 6 due to the
/run
directory not existing. It does exist on Centos 7 so I think it gets a pass there but I also wonder if it's wrong on there also despite.Cheers,
R.
The text was updated successfully, but these errors were encountered: