Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 265
  • Last Modified:

Having problems with a new apache installation

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
geekdad1
Asked:
geekdad1
2 Solutions
 
gr8gonzoConsultantCommented:
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
 
shalomcCTOCommented:
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now