Changes in apache-2.4.65-2 lead to webserver no longer starting

General system Applications
1

EDIT:

My guess the issue is related to symlinks was not correct. I have changed all config files to direct paths and the issue stays.

Using 2.4.65-1 everything is running fine, starting with 2.4.65-2 apache does no longer start complaining about directories are not accessible. But the directories exist and permissions are correct. This is the error message I see (for every vhost):

httpd[668417]: AH00112: Warning: DocumentRoot [/home/customers/webs/test] does not exist

httpd[668417]: (2)No such file or directory: AH02291: Cannot access directory '/home/customers/logs/' for error log of vhost defined at /etc/httpd/conf/sites-enabled/test.conf

But directories and files exist and are accessible by user http. How can I start httpd.service with more detailed logs (debug-logs)? Additionally I have a second server with mostly the same configuration. There newest apache starts flawlessly. The only difference I remember is that at the non functional the directories and log files are on another partition (but mounted and running on older apache version). This again is a guess for the reason - the above messages do not help because everyting is existent and accessible but apache cannot access them.

2

Take a look into the systemd service definition file for httpd/Apache2, maybe the service is started under a user that has no access to the directories it is referring to in the message.

3

Both versions are running as user http - there is no difference between the versions.

EDIT:

Now I am absolutley confused. Starting apache via systemctl start httpd.service leads to the error above. Starting it via console as user root with httpd -e debug is working! It results in 5 processes “httpd” running as user http ???

4

I got it. At the server which was not starting the web and log directories are under /home/customers. Starting with apache 2.4.65-2 there is the Option ProtectHome=on in systemd unit of httpd.service which protects /home from access. Removing this line fixes the issue.

1 Like
5

We can argue if this should be disabled in the first place, it is there for a reason i suppose.

So the real solution should be to move your dir’s outside /home

6

On a standard webserver there are no unpriviledged users with standard /home-folders, so /home is empty. The only server I own where this is different is the one where the problem popped up. So in my opinion this feature should be disabled by default… I cannot change partitions or other things to put the folder outside /home so for me I use my solution. I do not sleep bad doing this :grinning_face_with_smiling_eyes:

7

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.