Apache upgrade Troubleshooting Ideas

I upgraded our Apache server from 1.9 to 1.26.  But now the web pages aren't coming up.  I can go to the domain, and apache is running the correct version, but there is some kind of characteristic that is unknown to me.  For example, lets say you have the following structure:


In the cgi-bin, there is a script called: runit

This appears to be some kind of "doorway" to allow web pages to be served to the public.

The characteristics of the server are as follows:

http://www.-mydomain-.com  (Uhmm...this is is just an example, ofcourse)

If you go to this site, you'll immediately be redirected to:


Now...I've searched for a directory called: adirectory
And it doesn't exist on the server.  I can't find a reference to it...not even a symbolic link.  adirectory seems to be another name for the cgi-bin directory, because runit is located there.

After the upgrade...some kind of configuration was lost...

I'm not too familiar with apache.  I'm running it on a Solaris 8 SUN system.  So if you reply...speak slow...  :^)

I'd like to have anyones input on what they think is going on, and what I should do to try to fix it.  I normally give most everyone who replies points...because all expert input if valuable to me.  I appreciate any comments.
Who is Participating?
heskyttbergConnect With a Mentor Commented:

The LoadModule XXX is to load apache modules at runtime to keep down memory consumtion.

This is somewhat difficult to achive on Solaris and not to stable.

I got it working after a week of detective work.
It rquires quite a few extra paramters to configure if you want to use loadable modules in Solaris.

But if you need SSL I think you have to get this working.
I also requires the 'so' module.

It was almost 2 years since I did this in Solaris, you had to add some configure vairables like HTTPD_SHARED_CORE and ROW_CHAINING, I think it was in order to get dynamic modules.

When I did it I couldn't use the newest gnu compiler either there were som bugs in it.

As baeuml suggests there must be som sort of alias in order to get adirectory to work.

Either by a regular alias:
Alias adirectory "/www/cgi-bin"
<Directory "/www/cgi-bin">
  Options +ExecCGI
  Allow override none

For example, this requires you somewhere have AddHandler cgi-?? .pl .cgi

Or by the ScriptAlias.
But keep the cgi-bin ScriptAlias, copy that and name the new one to adirectory.

I'm not sure how that looks you can find it in your httpd conf somewhere ocmmented out.

/Hans - Erik Skyttberg
Look in your httpd.conf and change the ScriptAlias directive to:

ScriptAlias /adirectory/ /var/apache/cgi-bin/

A request for http://myserver/adirectory/runit will now cause the server to run the script /var/apache/cgi-bin/runit

rambleAuthor Commented:

Well...I've seemed to have installed this upgrade version of apache in a different directory than it was previously installed.  I see that the old httpd.conf file had a reference to it the script at:

/usr/apache/cgi-bin but it looks like I installed it at:

I changed the reference to match my new installed directory...and it didn't seem to help.

The old httpd.conf also seems to have a lot of: LoadModule XXX What does that do?

Take Control of Web Hosting For Your Clients

As a web developer or IT admin, successfully managing multiple client accounts can be challenging. In this webinar we will look at the tools provided by Media Temple and Plesk to make managing your clients’ hosting easier.

rambleAuthor Commented:
Ok...I've got one last question, then I'll close out this topic.

Since I've installed the apache in a different directory, I want to move, or delete, the previous installation.  However...the previous installation seems to have installed some files in several different directories, whereas the new installation is more central.  Is there a way to determine what files my current apache installation is using, so I can delete the other files?

If you are atlking about the Apache that comes with Solaris 8, this is installed all over the place.

You should be able to run the admintool, open the packages section locate apache and remove it.

Or use the pkg tools, I have no idea what the apache pkg is called.

This will stop the Solaris document web to function though.

/Hans - Erik Skyttberg
rambleAuthor Commented:

In response you your LOADMODULE...

If I used the old httpd.conf file, and "copied and pasted" the LOADMODULE from the old one, into the new one...do you know what kind of adverse effect that my have?

Thanks for you help.
rambleAuthor Commented:

You might get some errors if you don't have thoose modules compiled and then just need to remove them from the conf file.

You also may have to change the path to thoose modules.

/Hans - Erik Skyttberg
rambleAuthor Commented:

Just Ignore the last comment
All Courses

From novice to tech pro — start learning today.