Building a local yum repo, would normally download packages to /var/www/html/ and createrepo. The system I am working on, for whatever reason, was built with 20G /var and 195G /home. I did a reposync to /home/repodata. Trying to get httpd to be able to see fqdn/rhel-6-server-rpms.

So I have my repo at
drwxr-xr-x. 2 root apache 4096 Sep 10 16:35 repodata
[root@servername rhel-6-server-rpms]# pwd
/home/repodata/rhel-6-server-rpms

I went to /var/www/html/ and created symlink
lrwxrwxrwx. 1 root apache 34 Sep 11 13:48 rhel-6-server-rpms -> home/repodata/rhel-6-server-rpms/
[root@servername html]# pwd
/var/www/html

I did a recursive chown to root:apache on /var/www and /home/repodata
I did a chmod 755 on all same

Not sure what I am missing here.

When I view httpd ssl_error_log I see
[Tue Sep 11 18:00:10 2018] [error] [client xx.xx.xxx.xxx] Symbolic link not allowed or link target not accessible: /var/www/html/rhel-6-server-rpms

I have messed with my httpd.conf file and did
<Directory />
Options None
AllowOverride All (changed from None)
</Directory>

Options None turns off everything, including FollowSymLinks See the documentation

Changed options to FollowSymLinks from None, restarted httpd, same result

No leading slash on the link target? Typo here? or....

(Just grasping at straws here...we presume that the <Directory /> actually does point to /var/www/html?)

ln -s /home/repodata/rhel-6-server-rpms/ /var/www/html/rhel-6-server-rpms

Hi

It could be SELinux. I remember I had some problems with userdir on CentOS in the past. And I fixed it by adding some SELinux rules. Here's some info:

https://www.if-not-true-then-false.c...-red-hat-rhel/

Look in section 6. It could be you need something like this:

chcon -R -t httpd_sys_content_t /home/repodata

Thank you, I will try that as well. I had turned off SELINUX just to see if that was the issue, but the error persists. Really feels like a perms issue or security and of course the longer you look at it the more confusing. Shouldn't be that hard.

Hi

Then I don't know. But if all you need is a very simple web server, httpd is maybe overkill. Here's something very simple:

If you run this in a terminal, it starts a very simple webserver, and it's listening on port 8000 by default. And you will see the "log" in the terminal.

Will listen on port 80, but it requires root.

Thank you, I will try that........I was simply using httpd because it was already running on that box.