Apache 2.2 on FC5 and symbolic links/symlinks

pdevr99 · 06-12-2006, 11:29 AM

Recently upgraded to Fedora Core 5 (from FC4) which includes Apache 2.2. I've got a symbolic link in my /var/www/html directory to a development directory which worked fine in the old situation. With FC5/Apache 2.2 I get
"Symbolic link not allowed or link target not accessible"
messages in my httpd error_log (and no access to my files). I've tried about everything: file permissions, options in httpd.conf, etc, etc but cannot get it to work. Also cannot find any references to changes in either FC5 or Apache 2.2 documentation...VERY frustrating!

Anybody experienced similar things? Suggestions?

Tia,
Peter.

Aeternus · 06-12-2006, 01:01 PM

You mentioned "options in httpd.conf". Does that mean you've tried Option +FollowSymlinks ? (this may be something obvious, but "options in httpd.conf" is rather vague, sorry).

pdevr99 · 06-12-2006, 03:06 PM

Bit vague indeed, sorry. But yes, FollowSymLinks, SymLinksIfOwnerMatch, all that. I'm reading in other threads and forums that SELinux sometimes messes things up; my server is running with SELinux disabled.

grey_kristy · 08-01-2006, 05:59 AM

Quote:

Originally Posted by pdevr99

Recently upgraded to Fedora Core 5 (from FC4) which includes Apache 2.2. I've got a symbolic link in my /var/www/html directory to a development directory which worked fine in the old situation. With FC5/Apache 2.2 I get
"Symbolic link not allowed or link target not accessible"
messages in my httpd error_log.

Anybody experienced similar things? Suggestions?

Peter.

Please check full path to you work directory. I've got my work directory in my home, and home by default have permissions drwx------.
When I change permisions to drwxr-xr-x all work fine. So all directory in the path should be readable and executive.

erezhdd · 09-10-2006, 09:08 AM

I have encountered the same problem as pdevr99. However, I've also noticed that SELinux generates an error message in /var/log/messages whenever a browser tries to access a page that is sym-linked to /var/www/html. I have also confirmed that SELinux is responsible by turning off SELinux control on the httpd daemon (using the GUI tool for SELinux provided in System->Administration menu). This means that the problem is in the SELinux httpd policy, but I don't know how to tune it. Any suggestions?

Erez

mcupples · 04-05-2007, 03:56 PM

I've got a similar problem. My directories are as follows:

Code:

[root@69-64-69-24 www]# pwd
/home/www
[root@69-64-69-24 www]# ls -lah
total 60K
drwxrwxrwx 4 root root 4.0K Apr  5 13:50 .
drwxrwxrwx 5 root root 4.0K Nov 29 10:40 ..
lrwxrwxrwx 1 root root   26 Mar 23 06:36 ckesler -> /home/ckesler/public_html/
drwxrwxrwx 2 root root 4.0K Nov 29 10:40 css
-rwxrwxrwx 1 root root   24 Mar 15 06:40 googlehostedservice.html
drwxrwxrwx 3 root root 4.0K Nov 29 10:40 img
-rwxrwxrwx 1 root root 3.5K Mar 13 14:28 index.html
-rw-r--r-- 1 root root  35K Apr  5 13:50 index.php
lrwxrwxrwx 1 root root   27 Apr  5 11:38 mcupples -> /home/mcupples/public_html/
lrwxrwxrwx 1 root root   27 Apr  5 11:38 mmongeau -> /home/mmongeau/public_html/

Now, the only problematic thing is that /home/www is not a real directory but a symlink itself. The real directory is /var/www/vhosts/default/htdocs. I don't think there's any issue with that, I just set it up that way so I didn't have to type all that out every time I go there.

I would post my httpd.conf file here but I'm afraid I'll get yelled at. Instead, I just hosted it at http://mcupples.com. It's the index page.