Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What do you see in the Apache error_log (most likely located in /var/log/httpd)? My first guess is that you have a log file over the 2-GB size limit. It would really help to know what is being logged, though.
There is nothing in the Apache error_log about not being able to start up and it is only 160 KB. The log only shows stuff from the /usr/sbin/httpd (the working one)...
I also recently figured out that the problem was SELinux. I disabled SELinux for HTTPD and it worked but I do not know what in SELinux is causing httpd not to work...it is something to do with the httpd init script and apachectl cuz /usr/sbin/httpd works as I stated in my first post.
Ok. I figured it out. I have my DocumentRoot in my /home directory, therefore, I had to change the folder's security context to httpd_sys_content_t.
Then everything worked!
moenterprise,
I had to say, I don't think putting the document root in the /home directory can be a good idea. One little bug in your script can put your entire system at risk.
Rather, I'd recommend you to get the document root to be the default; /var/www/html (or /var/www/htdocs), I think that would be much better.
Changing permissions for the /home directory cannot be a good idea, and neither can it be a good idea to change permissions for the whole apache user/group.
Better still, put your document/scripts in some other partition of your hard drive, or in some other hard drive for that matter.
One of my friends' systems got compromised this way. ;-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.