Solved

Having problems with a new apache installation

Posted on 2013-01-10
2
259 Views
Last Modified: 2013-01-17
I've got a brand new Red Hat server 6.3 that I'm installing apache on.  I've run yum and installed apache 2.2.15

I'm basically cloning an older server so I've copies all of the config files over.  the problem is it's complaining about a ton of directives some of which don't apply until version 2.4 and others that are still valid.

It doesn't like
order allow,deny
SSLENGINE
SSLCertificateFile
BrowserMatch
DirectoryIndex   and others.

I'm getting to the point where I suspect the problem is not invalid directives, but some kind of configuration error in the build.

I shoudl also mention that I'm running selinux, but I've just turned it off to see if that was contributing to the problem, but got the same results.
0
Comment
Question by:geekdad1
2 Comments
 
LVL 35

Assisted Solution

by:gr8gonzo
gr8gonzo earned 250 total points
ID: 38767034
Copying configs is usually a bad idea unless you're a pro with Apache configs. Sometimes directive names or syntaxes change. In this case, all of the directives you've specified have been around for a while, but they are not built into Apache. They are bits of functionality that are added by extra plugins:

BrowserMatch - provided by mod_setenvif
DirectoryIndex is provided by mod_dir
Order is provided by mod_athz_host in 2.2
The two SSL directives are provided by mod_ssl

When you use yum to install Apache, sometimes it doesn't install all the modules / plugins. The yum repository often has these modules available as separate downloads to install. Something I usually do is:

cd ~
yum list > yum.list       <-- Creates just a cached copy of the yum.list command
grep -i "httpd" yum.list     <-- Search the cached copy for anything and everything Apache

If you want to look for something specific like mod_ssl, try:

grep -i "httpd" yum.list | grep -i "ssl"

You should be able to yum install the plugins to enable the missing functionality. I'm a little curious as to why the default install didn't have mod_authz_host and mod_setenvif already enabled, though. Usually those modules are common enough to be built into the server (it's not absolutely required, though, so...)
0
 
LVL 33

Accepted Solution

by:
shalomc earned 250 total points
ID: 38774006
it is possible that the modules are installed but are not enabled in the apache config file.

Look for a section with lots of LoadModule directives. Some are likely to be commented out.
0

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If your site has a few sections that need to be secure when data is transmitted between the server and local computer, such as a /order/ section for ordering or /customer/ which contains customer data, etc it would of course be recommended to secure…
I. Introduction There's an interesting discussion going on now in an Experts Exchange Group — Attachments with no extension (http://www.experts-exchange.com/discussions/210281/Attachments-with-no-extension.html). This reminded me of questions tha…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

680 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question